You’re offline. This is a read only version of the page.
We sometimes have users who do not enter a sales tax group code on one line of a sales order. When someone searches for a particular sales order by paging down, NAV throws an error that the sales tax group code is missing but doesn't give the sales order number. After this error, the person gets a blank list. The only way to fix this that we have found is to enter "TAXABLE" as the sales tax group code on the offending line and then everything works fine.
It appears that NAV is checking every single sales order when you page down the sales order list. In older versions of NAV, you would not get the error flagged until you posted the sales order.
Can anyone tell me if there is a fix for this problem?
*This post is locked for comments
You could modify the error message so that it includes the No. of the order that is missing the Tax Group Code.
Do you know how to do this? This article explains fairly well.
I have used the debugger and the error usually is a sales order line with a missing Tax Group Code. We have corrected the problem each time and put the Tax Group Code on customers so it defaults on new sales orders but the main issue is that NAV apparently scans ALL sales orders in on the list page. If the missing Tax Group Code is on the second page, the error is caught when you page down. NAV doesn't tell you which sales order is causing the problem. I understand that scanning all sales orders even though you are only looking at a list might be valuable but this error stops the entire company from working on sales orders when it happens.
I've started through the CUs and hotfixes but have not found the answer yet. Thanks for the suggestion though.
In addition to Alexander's response, if you are on an older build / Cumulative Update (CU) of NAV 2017, check this list of released CUs for NAV 2017:
support.microsoft.com/.../released-cumulative-updates-for-microsoft-dynamics-nav-2017
Here, you can click through the builds / CUs newer than the one you have, and look/search through the list of hotfixes in the build. Perhaps it has been addressed already in a recent CU.
I hope this helps. If my response has answered your question, please verify by clicking Yes next to "Did this answer your question?"
Hi Myrmel,
Which version of NAV are you using? Also, my suggestion would be to use the debugger in NAV and find which line of code is causing the error message.
This blog gives a pretty good explanation of how to use the debugger. https://saurav-nav.blogspot.com/2012/08/debugging-in-nav-2013-client.html
Regards,
Ted
Are you using US localization? To me it looks like a bug so far, which should be reported...
#1
Sohail Ahmed
2
#1
mmv
2
#1
Amol Salvi
2
Share
Report
All responses (
Answers (
