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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have a DMF processing group that runs as a batch job that runs daily looking for the existence of new files in a folder and create GL transactions. The batch could run for weeks without any issues until the error appears. It seems like DMF assigns the same Job Id again and again causing a duplicated index issue. After debugging the issue I got into the method and class that the system uses to create the Job Id. For some reason the DateTimeUtil::getSystemDateTime() method is getting the same date-time again and again. When AOS service is restarted, the batch job starts working again, and as I mentioned before it could work for weeks without issues.
Do you know of any issues with that method?
Why an AOS service restart temporarily fix the issue?
This is the error message. The system will try to insert the same job id every time it runs.
This is the part of the code that the job id is created.
You have a configuration of execution ID, date/time and a file sequence number. When the date/time will be the same (not sure why), the file sequence number will be the only part that makes the execution ID unique.
The Execution ID has a limited length. It might be the case that it can truncate the string when a new file number added to the string will exceed the maximum length of the Execution ID field.
Instead of the method DateTimeUti::getSystemDateTime(), you can try to use 'DateTimeUtil::utcNow()'
Thanks for your quick response.
Is this execution id configurable?
Where in AX it can be changed?
It would be possible to extend the length of the Execution ID field. You can also create a processing group with a shorter name, so there will be more characters left for the numbering.
Have you tried to change the coding to retrieve the date/time stamp?
Business Applications communities