Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
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
I am currently trying to find a way how to 'avoid rolling back' changes done to a field in a set of records after an error is encountered at a later stage i.e. say you have 5 records in total and you manage to successfully modify the field in the first 4 but if an error is encountered in record 5 then the first 4 records are saved with the change and not rolled back.
I am trying to avoid the use of COMMIT after every record change and was wondering if there is a way how to do it otherwise.
Just FYI , the change in the record is happening by calling a function in a codeunit. I have also tried to call the codeunit function from a report i.e. in report I have the below;
IF MyCodeunit.MyFunction(Record) THEN BEGIN
//Make field modification
Thanks in advance!
Why you don't want to use the COMMIT? You can use the CODEUNIT.RUN to catch errors but you still need to run COMMIT to update.
I don't think there is another way, cause if there is any error every thing shall rollback.
Thanks for your input :) It's not about not wanting to use COMMIT ... just wanted to check if maybe there is another way how to do it. Will still probably end up using COMMIT now.
Business Applications communities