Hello, one challenge on a CRM project is explaining why certain changes in CRM are "unsupported." My general explanation of this concept is that unsupported changes are not guaranteed to work and may break on a future rollup. Do you have a more articulate or complete explanation of what "unsupported customization" means in CRM? Also, do you have a good url that you have found useful to forward to people who challenge the concept of an "unsupported customization"?
I remember when I first started working on CRM I hid a ribbon button using jQuery and a more experienced CRM developer told me that change was unsupported. My logic was that clearly the change worked so wtf did he mean that the implementation was "unsupported". Of course, now I understand what that means and I have to explain this concept to others.
Based on my experience learning CRM I can understand why customers with a development background may challenge the concept of an implementation being "unsupported" in CRM so I'm trying to identify the best possible explanation and url reference that I can reuse to help others understand this concept.
*This post is locked for comments
I have the same question (0)
