New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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
This post is part of a series of posts on implementing Jet Reports and is part of the Jet Enterprise sub-series.
In the last post, I stepped through the creation of an execution package; I am going to set this to execute automatically on a schedule, but first I am going to manually run it to ensure that it works.
To test the execution package, select the Execution tab, right click on the execution package to test and click Execute:
Review the Tasks and then click Start:
Once the execution has completed, without displaying errors, click Close:
Launch the Windows Event Viewer and check for a success message in the Applications node under Windows Logs:
Now that we have confirmed the execution package can be successfully executed, in the next post I will schedule it to run automatically.
Read original post Implementing Jet Enterprise: Test Execution Package at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities