The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Picklist
Posted: 20 Jul 06 1:05 PM
|
fiogf49gjkf0d The Sub-Type field changes. For example, I select "mm corp" for my Sub-Type it will change itself to K6UJ9A00020V. I check to see if itwas populated correctly in the picklist and it is. Any suggestions or ideas what might cause this? |
|
|
|
Re: Picklist
Posted: 21 Jul 06 6:11 AM
|
fiogf49gjkf0d The sub-type field takes a little to get used to at first. The first thing to understanding it is it is linked the type field. This can be rather annoying depending on your use of the sub-type field. So it might look like this
Type SubType
Prospect Prospect SubType A
Prospect SubType B
Prospect SubType C
Customer Customer SubType A
Customer SubType B
Customer SubType C
This sounds like what you are describing to be the issue. You have to remember that for each Type there is a different sub-type list.
John G. |
|
|
|
Re: Picklist
Posted: 26 Jul 06 3:01 PM
|
fiogf49gjkf0d Mine does seem to be set up that way. No matter what Type I choose the subType list is the same. They are two seperate pick lists and don't seem to be related. Is it set up wrong? |
|
|
|
Re: Picklist
Posted: 26 Jul 06 6:04 PM
|
fiogf49gjkf0d You have to create an "Account Type" picklist for each type. For instance one of our types is "Carrier" so I have Account Carrier as the subtype picklist. This is completely independent from Account Prospects or Account Customers.
One problem I had with this was that the stock SalesLogix code assumes a picklist is created. If Account Carrier is not a picklist but you change the type to match, the picklist no longer shows anything which I found to be very annoying. I now include a check to verify the picklist exists in the database and the subtype.text is not in that picklist before resetting it. There are no values that overlap but in the rare instance that does happen I don't want users to have to reenter values. They'd forget to verify the data either way but I'd rather err on the side of caution. |
|
|
|