web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Business Central forum / Edit in Excel issues i...
Business Central forum

Edit in Excel issues in in a multi tenant environment D365 BC Spring 2019 Update

(1) ShareShare
ReportReport
Posted on by Marco Mels Microsoft Employee

Hello,

We did recently discover an issue with the Edit in Excel functionality when working in a multi tenant environment in an OnPrem scenario. As per the requirements, Edit in Excel does require host name rewrite rule to be enabled in the web.config file of the relevant WebClient instance. Unfortunately, the tenant host name gets lost as we could see in a Fiddler trace. This is happening since the release of the Spring 2019 Update.

When Fiddler is not running:
0525.1.PNG

When Fiddler is running you will see the following error:

3240.2.PNG

We wanted to inform you that this is an issue not yet reported by any partner. We are working hard to mitigate it. If there is an update, we will post it here.

Thank you.

Categories:
Other
I have the same question (0)
  • Suggested answer
    Marco Mels Profile Picture
    Marco Mels Microsoft Employee on at

    Update: The issue has been resolved in build 14.31661.

    In a four tier environment (IIS / SQL / NST / Client are on different servers) we do require some additional configuration to be done. We were able to get the proper OData URL domain replacement set up in a build that has the fix for it. It was failing to replace the domains until both the domain in PublicODataBaseUrl and the domain specified in the tenant’s AlternateId resolved to the same IP via DNS. In a multi server scenario, the OData endpoint (NST server) differs from the Web URL endpoint (IIS Server). Adding a second alternative ID and pointing the right one to the OData endpoint in DNS will mitigate the scenario.

    Adding a second alternative ID can be done via PowerShell:

    Mount-NAVTenant -Tenant <<string>> -ServerInstance <<string>> -DatabaseName <<string>> -DatabaseServer<<string>> `

    -DatabaseInstance <<string>> -AadTenantId `xxx.onmicrosoft.com -AlternateId @( "mytenant.domain.com", "odata.domain.com" ) `

    -DefaultCompany <<string>> -DefaultTimeZone <<string>>  -EnvironmentType <<string>> -OverwriteTenantIdInDatabase -Force

    where mytenant.domain.com points to the IIS servers IP address  and odata.domain.com points to the NST servers IP address in DNS.

    Thanks.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Business Central

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans