If you were to imagine a custom form in Microsoft Dynamics CRM where you could select any entity and any field on that entity you would realize a few things about option sets.
To enter and support every entity and field would be a daunting and impossible task. Even if you were to spend the time tackling the previous hurdle, any customizations you made to those entities would have to be tracked and re-applied in the option sets, thereby duplicating your workload.
This really wasn't a viable solution dynamic options what is it what we were trying to do either. The solution we came up with was to utilize single line of text fields hidden on the form to store the values for our option sets.
We'll demonstrate this with one mapping field. So let's start by setting up our form.
Latest Blog Posts
If you do plan on implementing this there are places where refactoring should be performed and efficiency improved.
- During periods when a trade signal does not indicate a trend in either direction, the strategy will signal investing in cash.
After we've received the XML response back from the request, we loop through each attribute node in the document and use XPath statements to grab both the display and schema name. Finally, we create option elements, fill out their value and text attributes and add it to our option set.
Now that we have a helper method, which will populate our control, we need to call it from an event and pass it a value. For this example, we'll utilize the onLoad functionality of our form and hardcode the value lead to be passed to our helper method.
Latest PO TV Videos
Once published, you should be able to create a new mapping entity from CRM with a dropdown that is populated with all available attribute or field names: Now that we've got the values in a dropdown, we need a way to store them. Since this isn't a real option set as far as CRM is concerned, it won't pass back any value.
If you create a new Mapping Entity and select an option from the dropdown, you should now see the Selected Mapping Dynamic options what is it field populated with the schema name of the attribute: This new value will persist when saving the entity. We can now hide this field if we wished too. It is now just a friendly storage site on your form. There's one piece of the puzzle left and that's how to handle when the page loads.
Automatic tokenization into tags
If we were to load the page as it exists, our hidden field would contain the schema name of our attribute, but the dropdown would only have the default value selected. There you have it. Happy CRM'ing!