Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
The last post I did was on Hands On With MDGP 2018 RTM New Features: Workflow Additional Fields, which included details on some errors I was encountering with the EFT fields. When Dynamics GP 2018 was announced, I heard that not only were these fields being added to the notification email, but that a user changing them would force the vendor to be resubmitted to workflow for approval.
The testing I did suggested this wasn’t happening. So, I wrote up a bug report with details of the errors and effect and sent it to Microsoft. This has now been written up as a bug for the development team to look into.
Nice to know that a fix is being looked into, it’s just a shame that it’s going to be a little which before this feature will be available; EFT payments is how 95%+ of supplier payments are made by my clients.
Read original post Microsoft Dynamics GP 2018 Vendor Change Workflow EFT Bug at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities