Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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
Upgraded from Microsoft Dynamics CRM 2015 Version (188.8.131.52) (DB 184.108.40.206) on-premises to
Microsoft Dynamics CRM Version 1612 (220.127.116.11 (DB 18.104.22.168) on-premises.
Also, using Windows 10 Enterprise Version 1809 OS build 17763.1697
And, Microsoft Excel 2016 (16.0.4966.1000) MSO (16.0.5095.1000) 32-bit
With CRM upgrade, we started getting the following error when exporting a Dynamic Marketing List using a View with a Related Entity Column (NOTE: The Related Column appears Blank on screen)
It doesn't matter whether the Export is to a Static Worksheet, Dynamic Worksheet or Dynamic PivotTable.
[white X in red circle) Failed to Generate Excel
An error occurred when Dynamics 365 tried to generate the Excel file. If this
problem persists, contact your system administrator
There was no issue with our previous version: Microsoft Dynamics CRM 2015 (22.214.171.124) (DB 126.96.36.199) on-premises.
But now, any user, in any country, with any Security Role, on any server (all same version) or database that has tried has the same issue, even me, the System Administrator.
There is no issue exporting to a Static Marketing List and there is no issue if the View only has columns from the existing entity, no matter if it uses Accounts or Contacts (we don't use Leads)
Sounds like a fairly generic error in the UI. I would suggest to enable platform tracing on the CRM web front end server when reproducing the issue and check the trace files for the related error to get more details:
Thanks Alan. We'll give it a try and post our findings.
Business Applications communities