Thursday, February 14, 2008 3:49 AM
V4 - Trying to create a workflow that creates another record (custom project table) when an opportunity is closed. It seems that picklist values mapped between tables do not respect the mapping when created thru workflow (not all too surprising) but also, in workflow I can't seem to see where you can map a picklist field to equal the parent record's picklist field value. Simple example - created a rating field in the custom (1-M) project table and tried to simply make it match the rating of the opportunity when created. When you select that picklist, no options are presented to select other than a default value or in the field itself, selecting one of the values of the picklist. Please tell me that i'm missing something or that this is a known bug scheduled to get fixed.
Friday, March 07, 2008 9:01 AM
Hi Ray, Picklists are ultimately enums of different values. Workflow will be able to map the values provided you have matching values in *both* picklists. e.g. if you create the Opportunity Rating picklist with values 1=Rating1, 2 = Rating2, 3 = Rating3; and the add the same set (1 = Rating1 etc) to the Project.Rating picklist, you'd be able to map them using workflow.
Alternatively, mapping can also be created without adding it to the workflow - by using the relationship mapping feature (Create a N:1 relationship in the Project entity - N Projects: 1 Oppty) and create additional mapping in that relationsihp to map the picklist from source (opportunity) to target (project). Note that you'll still need to create the picklist values in both attributes (and map their numbers to each other exactly). Once you create this mapping, when your workflow kicks off and the Project entity instance gets created, it will automatically use the opportunity.rating value and set the project.rating value.
Hope this helps.
Tuesday, March 18, 2008 8:06 PM
I am having the same issue....create a custom record when opportunity is closed, everything maps over fine except for the picklist. Did you manage to get this issue resolved?
Saturday, March 29, 2008 2:40 AMMicrosoft has confirmed that this is a bug and is working on a hotfix
- Marked As Answer by Ronald LemmenMVP, Moderator Thursday, April 23, 2009 9:09 PM