Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Business Central updates!Learn about the key capabilities and features of Dynamics 365 Business Central and experience some of the new features.
Download overview guide | Watch Business Central video
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have this error when I try to connect my BC test company to PowerBi.
I have tried to follow the other examples stated here at the forum, but with no luck.
Anyone who can help me where to set-up the correct reply url?
I am all new in setting up PowerBi to BC,
Please explain a few more details
how you are trying to connect BC test with power bi..?
BC is on-premise or Saas..?
Mention the URL..!
did you enable Odata service..?
If you managed to resolve your issue, please mark all helpful answers as Verified - this would indicate to similar forum members that your issue has been solved.
I followed the 'Get started with PowerBi'. I had to have administrator to do some authorization log-in and approve the permissions. And after that I had the error message shown.
It is BC on-premise.
The url is; tftest.officeconnect.dk:49004/.../
Then I tried af few editing on azure portal on the url settings.
Hmmm, I have no idea how to enable Odata service. So maybe that is the case.
If you run the Assisted Setup, you can connect to Azure AD. Here you authenticate yourself. If you did run this before with incorrect PublicWebBaseUrl, it will not do it again. Then you do need to correct it in Azure portal.
The PublicWebBaseUrl is like nav.yourdomain.com:port/.../
In the Azure AD App, a html file is added so that the landing page will become:
The Azure AD app is called (you can find it in App Registrations in Azure Portal, All Applications):
Microsoft Dynamics NAV Application
Personally, I do usually add the NST instance name to it so that it does become Microsoft Dynamics NAV Application BC140, this is however not required. In my scenario I do have multiple releases running on the same box which means multiple registrations. Here you will find two reply urls. The above one and the actual PublicWebBaseUrl plus /SignIn.
Earlier I did mention that the SignInAudience of the created AD App must be AzureADMultipleOrgs. It does however create AzureADMyOrg. You can correct that in the Azure AD App manifest file (you can retrieve that via the browser).
Hope it does help.
Business Applications communities