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
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 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
Every month end, when I try to get the NACHA file to be loaded in the bank, I get the error below. The only solution I get is by removing lines by trial and error.
This is cumbersome as this process is time sensitive. I have been with the team for about 4 months and it keeps happening! When I asked my team, they said they have had it for years and technical team can't seem to replicate it so the issue keeps happening.
This one is tough to know which field is the culprit. I would call your Partner and have them debug this to tell you which field is the issue in your Data Exchange definition. Then you can repair.
Hi, From the error message you provided, it looks like this function below is causing the problem.
PADSTR Function (Code, Text):
Now is '-1'.
I agree with Steve, it still needs to contact your partner to optimize the code.
Hope this will help.
Thank you Steven Chinsky ZHU YUN , I have been trying to work with our partner and it is still outstanding. The team has had the issue close to a year now. Hopefully they were able to replicate it last Friday when I informed them. I haven;t heard back from them though.
Just to add, it happens when I extract NACHA files that are more than 100 lines and with 2 posting dates. I tried having 2 posting dates with a file with only about 10 lines and it worked.
Lines I know would not be an issue. I have never tried to create a NACHA file with 2 different Posting Dates within the Payment Journal but I cannot think why this would cause an issue.
Hopefully your Partner can reply Monday.
Oh I see. Okay, so I'm back to the idea that one of the lines is causing the error. Hopefully! Fingers crossed!
Business Applications communities