Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Wondering if anyone can help a total newbie to Dynamics 365. Have started working on an existing implementation of Dynamics 365 (on premise) and am told by current developers that under no circumstances can I amend a column in a table for one of our entities directly on the DB. I am simply wanting to default an INT column to value 1.
They tell me "Dynamics is a black box and you will be breaking the law if you amend directly". This can't be true can it?
Thanks for any advice you can offer.
Yes, your colleagues are right, you should not apply this kind of changes directly in the database, never. It will brake the system in a unpredictable ways and it will be hard to fix it later.
You can define a default value to an attribute in a Form in supported way, through Dynamics, for example using Business Rules or Jscript etc
Doesn't this mean I need to add default values for the same property in every form in the system? If I have > 1 location where I can create/update an entity then this rule needs to be applied to each instead of a simple database level constraint? Seems mad to a newbie!
As already stated generally touching the database is not a supported customization, but some performance type activates are allowed (technically, if you do make unsupported customizations and end up 'breaking' something Microsoft can decide to not help you fix things). This is how it has been for years and is unlikely to change (and in Online you can't even see the Database). You need to remember that Microsoft have a lot of logic built into their layers above the database and any change you make could inadvertently impact it.
Hi Paul Moores,
Writing directly to the Dynamics CRM SQL database is not a supported activity. Do it at your own risk.
Business Applications communities