Get Ready for the Next Release of Microsoft Dynamics CRM
Problems configuring the CRM Outlook client? Use the wizard!
Customer Center for Microsoft Dynamics CRM 2013
Customer Center for Microsoft Dynamics CRM 2011
Technical Support FAQ: Online | On-Premise
Developer Center and SDK
For Accounts, Contacts, Opportunities, and Cases, in CRM 2010, we moved 2 fields per form and added user-defined values to "option set" fields. For weeks, we troubleshot why those UD values would disappear or co-mingle with the generic values over and over again.
After the 2013 upgrade, the same issue has re-appeared. Some of the option set fields are changed in nature. Now they're a quarter-inch high and make it EXTREMELY difficult to make a selection. Our user-defined values are either missing or again co-mingled with the default options.
This recurring problem has done a good job of totally destroying CRM 2013's usefulness for us. Our data is corrupt. Views set on them are incorrect. It's a mess.
I don't know what technical level to address this on without additional information, but here goes.
The height of the option set/dropdown field is currently slightly bugged. To fix this, go to the form editor of your form and highlight the option set field. Then, click the "Insert" tab up top and add one or more "blank fields". Not quite sure about these translations, it may be called "White Space", "Separator" or something of the like.
This gives your option set field more space to expand until these fields are fixed.
Do the option set fields use existing, global option sets, or are the options defined directly in the field details?
Find out this by double-clicking the option set field on the form editor and select the "Details" tab. Clicking "Edit" here opens up a new window where settings for the field are specified. Check whether "Use existing option set" is set to yes.
If they use existing sets, find the option set(s) in question in the "Option Sets" tab of the "Customizations" menu under "Settings" and make sure none of them share the same name and that the options they contain are the correct ones.
If the options are defined directly in field details, verify that the list contains only the correct values.
I'm struggling to follow what's happened. At first it sounded like a display issue but then you mentioned data corruption so I'm not following. Maybe you could provide a more clear example and we might be able to better assist with suggestions.
Best Regards, Donna
CRM Architect, Hitachi Solutions
Blog | Twitter | LinkedIn | Microsoft CRM MVP | Rockstar 365
This solves the field size issue. The fact that generic values are co-mingling with user-defined values is a return of the same bug support resolved for us when we initially implemented online so I will have to deal with support again.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics