Steven
asked on
CRM 4 - Add additonal required fields to Sales>Opportunities
Running CRM 4 and the sales manager would like to see a required field, drop box to be exact, to the Sales>Opportunity section. (see ss1)
We would like this drop box to be titled Sales Cycle with the following fields:
Not Qualified Lead
Qualified Lead
Requirement Established
Demo (Pre-Sales)
On Confirmed Shortlist
Preferred Vendor /Negotiating
Contract/Client
So how can this be achieved?
ss1.png
We would like this drop box to be titled Sales Cycle with the following fields:
Not Qualified Lead
Qualified Lead
Requirement Established
Demo (Pre-Sales)
On Confirmed Shortlist
Preferred Vendor /Negotiating
Contract/Client
So how can this be achieved?
ss1.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yep.
Value is a unique Index value that CRM assigns to each item in a picklist. Unless you are referencing the field in client side code (javascript on the form) or using the SDK (i.e. VB or C# code that interfaces with CRM) you really don't need to worry too much about the Value.
One other area where you might need to worry about Value... if you create a picklist on a Lead and you want it to map to the same picklist on the Opportunity, then you need to make sure that the values between the two forms match. That goes for any other mapped pick lists.
The more technical description is that Microsoft CRM stores these picklist values on a separate lookup table and stores only the Values in the actual table (I don't know the reason why ... but probably to cut down on the # of bits in each SQL row). They do a pretty good job of making this transparent to the end user and to the developer - but there are a few "gotchas" as described above.
Value is a unique Index value that CRM assigns to each item in a picklist. Unless you are referencing the field in client side code (javascript on the form) or using the SDK (i.e. VB or C# code that interfaces with CRM) you really don't need to worry too much about the Value.
One other area where you might need to worry about Value... if you create a picklist on a Lead and you want it to map to the same picklist on the Opportunity, then you need to make sure that the values between the two forms match. That goes for any other mapped pick lists.
The more technical description is that Microsoft CRM stores these picklist values on a separate lookup table and stores only the Values in the actual table (I don't know the reason why ... but probably to cut down on the # of bits in each SQL row). They do a pretty good job of making this transparent to the end user and to the developer - but there are a few "gotchas" as described above.
sknoll84,
Did the above information provide the solution you were looking for? If so, can you go ahead and accept the answer?
Thanks.
Did the above information provide the solution you were looking for? If so, can you go ahead and accept the answer?
Thanks.
ASKER
Can you please explain Value, after click Add in the picklist options? (see ss2)
ss2.png