ArcherPoint Dynamics NAV Business Central Developer Digest - vol 323

ArcherPoint Dynamics NAV Business Central Developer Digest - vol 323

This edition of Developer Digest includes BC’s upcoming Report Extension Object Model, a print preview Issue in BC 17, and waiting for a 1099-NEC Report for tax year 2020 in BC.

The Dynamics NAV and Business Central community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of  sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media…so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV/BC experts and devotees around the world. We hope these insights will benefit you, too.

Report Extension Object Model Coming Soon to Business Central

Saurav shares: “Report Extension is on the way; be ready. See Peter Borring’s comments on github. and then cast your vote for the Report Extension here: Microsoft Idea – Report Extensions should be introduced (

Figure 1 – Report extensibility in Microsoft Dynamics 365 Business Central

Dynamics 365 Business Central Office Hours with Microsoft

Kyle has good news: BC Office Hours calls are back, at least for December.

Print Preview Issue in Business Central 17

Bill W warns: “Heads up: BC 17 has a new feature that keeps the print dialog open if you use the “Preview” option. This is causing the OnOpenPage trigger to run twice before print output. We noticed this was causing some variables set to default in the trigger and exposed on the Request page to always be what they were set to in the trigger. The result was/is the report options didn’t do anything.”

Kyle replies with the feature page for report request page can open multiple views from Microsoft.

Bill W answers: “Thanks for the link. I didn’t find that in my scan of new features; that’ll help if I can find the right spot to report the bug.”

Bill adds: “Here’s the response on the bug report: 

I understand that you’re seeing different report behavior in v17 of Business Central. I looked into this and found that it had already been submitted to Dev as a bug, but it came back as ‘By Design’. Here is the information as it was submitted and the response.’

Previously, in v16.5 of Business Central, the OnOpenPage trigger for Reports was only run when the Report Dialog first opens.
Now, in v17 of Business Central, the OnOpenPage trigger runs both when the Report Dialog opens AND ALSO when the report is actually processing (after clicking Print or Preview in the Report Dialogue page). We have determined this because our extension code in the triggered twice, all our reporting logic is broken.
Current Behavior: For reports, when the report’s request page opens, the trigger OnOpenPage runs. When a report is run through either the “Print” or “Preview” actions, the OnOpenPage runs first, and then the OnPreReport runs. When a report is run through the “Send to…” action, only the OnPreReport runs.
Expected (Old) Behavior: For reports, when the report’s request page opens, the trigger OnOpenPage runs. When a report is run through any of the actions (“Print”, “Preview”, “Send to…”), only the trigger OnPreReport runs.
Dev Response: This is by design as the new paradigm is that we always ‘schedule’ the report – and when doing a preview, we effectively ‘schedule immediately’ and wait for the result. So, there are two report instances at play—each raising the event once. We are introducing a new property, ‘AllowScheduling’, if you want to opt out of this behavior. For now, you can mitigate by setting SaveValues = false’

The new property they are talking about, ‘AllowScheduling’, is in update 17.1, which has already begun to roll out to anyone on BC 17.”

1099-NEC Report in Business Central

Kyle asks: “Does anybody know anything about the new 1099-NEC form for tax year 2020? I just checked and even BC17.1 doesn’t have that report available.”

Crystal T responds: “I sent a case to Microsoft a couple months ago to see when they would be publishing this change. They are waiting on the government to publish their changes, and then they will do whatever they need to do to accommodate those changes. I suggest that the first person to hear anything posts in Yammer as there will be plenty of customers waiting on it.”

Kyle notes: “The 1099-NEC, Nonemployee Compensation Form information been on the IRS website, I think since springtime.”
Crystal adds: “There is an updated reply from Microsoft: they will wait until they are sure there are no more changes to the 1099 (besides the NEC one) and then they will publish their changes. They don’t want to submit this change and then the government decides there’s another one. This change is on hold until then. It will most likely be late 2020 or even early 2021

Kyle has more: “I am hearing rumors that this now involves states, too—that they want a magnetic file, too. When did Microsoft last update this support case?”

Crystal replies with a response from Microsoft that states: “Thank you for the posts and everyone who has provided guidance on this issue. Microsoft Dynamics Business Central and NAV Global Development is in the process of creating the new report. The new 1099-NEC Report will release in cumulative updates for Microsoft Dynamics NAV 2016 through current versions. In addition, the 1099 MISC will include the change for the removal of Box 7 as Non-employee Compensation and restructure under the new 1099-MISC format for 2020 filing. At this point, we do not have the timing on whether this will be included in the December or January cumulative update release. For Microsoft Dynamics NAV 2015 and earlier, the report will need to be pulled from NAV 2016 and brought back as these versions are no longer under current Development support with the five year lifecycle, or custom development of the Report will need to occur.”


If you are interested in Dynamics NAV and Business Central development, be sure to see our collection of NAV/BC Development Blogs.

Read the “How To” blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

Trending Posts

Stay Informed

Choose Your Preferences
First Name
Last Name
Subscription Options
Your Privacy is Guaranteed