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.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Created a new field in CRM 365, for ex Column2
I would like to update all rows from Column2 to be equal to Column1, column 1 and column 2 have the same data type. Would there any problem if we use sql scripts to update the new field?
SQL script to update Column2Update Table ASet Column2 = Column1
Would there any issues/risk in using SQL updates?There are thousand of records to be updated, therefore using the supported method would take time. We only need to update Column2 from Column1.
The way you describe is called an "unsupported" way of data manipulation and it is not recommended.
Using SSIS and Kingsway Soft adapter could help to update the data in a supported way.
The main issue with direct update is the fact that backed (plugins/workflows) won't react on this update if it is needed. And that's pretty much it.
I can't say it was the usual goto for me but I did direct updates and I don't remember any harm to the DB caused with such kind of data manipulation.
How did you do your direct updates if it wasn't via SSIS?
Business Applications communities