Customizing Dynamics NAV
Discover different ways to customize the application to give you and your colleagues access to the features, functionality, and data that you need most.
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
Scenario: I had created an action button Print to run a report using REPORT.RUNMODAL, while running this report from the Windows Client an error is thrown as below.
Microsoft Dynamics NAV 2017
RUNMODAL stops the transaction and waits for the User interaction. Hence, all users are blocked (who need the table).
During a transaction, we are not allowed to open a object with RUNMODAL.
Use COMMIT statement before you call the REPORT.RUNMODAL.
What does COMMIT statement do?
The metasyntax below contains two write transactions. As execution begins, a write transaction is automatically started. Using the COMMIT function, you tell the system that the first write transaction has ended and prepare the system for the second. Once execution has been completed, the system automatically ends the second write transaction.
(C/AL Statements) // Transaction 1
(C/AL Statements) // Transaction 2
The post Error Resolution to “Form.RunModal is not allowed in write transaction” in Microsoft Dynamics NAV appeared first on CloudFronts - Microsoft Dynamics 365 | Power BI | Azure.
Business Applications communities