Recently I have discovered what I believe to be a bug with the way workflow handles a pre-validation exception that is raised to it via a plugin. This issue has forced me to perform pre-validation in the pre-operation stage with steps lower than my actual pre-operations. This however seems to have a draw back as well.
I’m not sure if this issue is just tried to the ribbon but I lost quite a lot of dev time today trying to figure out what was happening. Take this post as a heads up just incase you get the same issue. Part of a product I am developing requires a silverlight application being started from the click of a ribbon button. However after altering the XML for the ribbon my changes weren’t being displayed.
Typically a CRM system would capture data for a range of system users. Even though these users may be capturing the same type of data they may be entering it differently to each other. For example the same address can be entered in many different ways. CRM Codex’s Formatter allows text fields to be formatted in order to keep to a defined format. The formatter will work on an attribute-by-attribute basis, which can be specified by the CRM system customiser.