???? ???????????????? ?????? ?????????? ???? ?????????? (???????? #??)

Have you ever wondered why your CRM system tends to get slower and slower by time?

Have you felt the pain that when you fix a bug or add a new functionality, an old functionality breaks?

Does every time Microsoft comes with changes or deprecations, some of your functionalities break?

 If the answer is yes, probably you are in the ?????? ???????? ?????????????????????????? ????????.  

Most of the clients I have worked with, regardless of the size, fall into this trap thinking that too much customization will help them to have easier and faster automation. This sounds true, whoever it comes with a cost. 

 Here are the symptoms of too much customization tarp, why to avoid them and the alternative solutions ??

• So Many JavaScript,
• So Many Plugins
• So Many Custom Workflows

?????? ???? ?????????? ????????

1- More custom code means more processing time needed, which leads to slowness to your CRM system.

2- Every time Microsoft deprecates some code, an extra effort is needed to replace the deprecated functions/code with the new code, which means extra time and money.

3- Continued changes to the custom business processes leads to, by time, massive code changes. If not done carefully, can lead to other functionalities breaking, which  means extra time and money to fix what got broken.

4- Logging, if not done and setup wisely, can easily take from your tenant space, which impacts performance. 

 ?????????????????? ?????????????????????? ????????????????

1- Try to use Business Process Flows and Business Rules as possible

2- Try to use OOB functionalities as much as possible

3- Try to use Power Automate/Flows as much as possible 

Do you agree or disagree? let me know what you think and comment below

 #msdyn365 #CRM #salesoperations #salesops