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
We've been testing the Making Tax Digital functionality using various versions of Dynamics NAV on-premise. We've used the Client ID and Secret published for Dynamics NAV Business Central and noticed that when logging on to the HMRC website to sign up for the service, the software prompted is Dynamics 365 NAV Business Central not Dynamics NAV. HMRC have two approvals for the software - one for Dynamics NAV Business Central and one for "plain" Dynamics NAV.
Does anyone know if the Client ID and Secret are the same for all on-premise versions of NAV or is there a separate set for "standard" on-premise versions of NAV and if so, what these would be?
We have the same "issue". Cannot find another Client ID / Secret anywhere... When I try to set the code in NAV 2015 CU53 for the Authorisation with our customer, we get an error message:
Write Authorisation failed.Reason: Http error 400 (BadRequest)code is invalid
I will reply to your thread if we found some information about that.
Hi Timon, thanks for getting back to me.
I’m fairly sure that the Client ID and Secret in CustomerSource applied to all versions of NAV but it would be nice if someone could confirm that this is correct.
I’ll update the thread if I hear anything.
We are getting a similar error, we have again used the Client ID and Client Secret as provided by the Microsoft Blogs that has worked for D365 BC.
Our Error is: Authorization Failed. Reason: Http error 401 (unauthorized) Client ID or Client Secret
Has anyone been able to setup a NAV2015 > NAV2018 or even D365 BC On-Prem.. although that is another issue! with the provided Client ID/Secret
D365 BC On Prem, doesn't seem to have the required objects! or Coneunits! as Microsoft have stated in the blog!
I suppose we are all getting close to customers wanting this setup and configured ASAP..
The credentials you're supplying are for the Live site so it may be that that isn't up and running yet so that may be a problem with the HMRC site (it doesn't have to be until next month after all). That said....
As you say, the latest on-prem version of BC doesn't have the MTD objects pre-installed. I guess you could use the 2018 objects but it would be nice to sure.
Microsoft have just informed me that the MTD functionality is actually an Extension and is installed already :-) just checked and bingo, its there.
Hasn't helped yet with the issue of the Connection as above, but using the same details it worked for D365 BC online.. so why not for On-prem..
Thanks for the update. One down, two to go....
Were you trying to sign up a real customer when you saw your errors or doing this as a test in the pilot?
Did anyone get this working now the 1st April is past and the system is live? I am getting an error on NAV 2017 saying
"Http error 403 (Forbidden). The client and/or agent is not authorised." when I try to retrieve VAT Return Periods.
I was able to get the authorisation token ok.
Some more twists to this tale. Has anyone been able to sign up for MTD using an on-premise version of NAV or Dynamics 365 yet using the 365 Client ID and Secret?
There's also another issue that appears to have emerged. Microsoft have released an update in the latest Cumulative Update (April) which appears to strip out any minus sign (-) from the Box 5 value submitted to HMRC. But a negative value is quite common and is quite valid. It should not occur for the other values submitted to HMRC though. I'm wondering if this change is correct? We're certainly sitting on this update and not releasing to to customers until this is clarified.
Does anyone have any more information on either of these two issues?
I've now got some clarification on the two issues:- The Client ID and Secret used for on-premise versions of Business Central is also valid for Dynamics NAV.
Also, the latest fix released by Microsoft is valid as HMRC will not accept negative values in the submission file. If the value in Box 5 of the VAT Return means a repayment is due, HMRC will work it out based on the other figures on the Return.
This all just about resolved.
Great thanks for the update Martin. We are rolling this out to our customers in the next couple of weeks.
Does anyone know how we request the Client ID and Client Secret through Partner Source? I am not sure where or how to request it. And how long it takes from request to receipt?
Also does anyone know if the service connection api is done through the client or the server and whether we would need to open things up on our cloud infrastructure that NAV2018 is hosted.
You can get the Client-ID /Client Secret in this link: mbs.microsoft.com/.../365dynamicsbctaxdigitsupinfo (Legit for all NAV Versions from 2015-BC)
I cannot answer the Cloud question though... I think its done over the Client but not sure about that...
Thanks Timon! That's a real help. I have just put it into our system and Clicked on request the Auth code icon and it took me to the HMRC webpage. So I think it must be through the client and doesn't appear to be an issue.
We have signed up for HMRC and got a valid access token back and pasted it in the service connection setup for HMRC. When we go to Vat Return Periods, click on the button "Get Vat Return Periods" we get this error "Http error 403 (Forbidden). The client and/or agent is not authorised."
Refresh token is successfull when we try this from the service connection.
SOLVED! It was the external accounting lady trying to request the access token, when we requested the token with another internal user from the company, it worked!
Business Applications communities