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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
when exporting from CRM 2013 (SP1 UR4) view to excel (xlsx), for related entity columns, they appear twice on excel headers. Please look at this example:
View in advanced find:
View in excel
Does anyone know how to avoid the second entity name between brackets?
Thanks in advance!
This certainly looks familiar, but I was not able to determine if this was a registered issue with CRM 2013. Allow me some time to research and I will let you know what I find out.
Looking into this, I could see that this is intended behavior that is still present today in the current Online and On Premise client (Ver 9.x).
To add a little more context to what is going on here, the naming convention is "FIELD Name (entity context) (entity)" For example below I added two columns to a User view. The first was the Calendar Type from the Calendar entity, and the other was the Address from the Created By context of the User entity.
This was implemented at some time in the past to avoid a duplicate column error that would occur within our process to create this sheet if you used multiple values with the same name from different or even the same entity. At the time the only workaround was to either rename or not use the column. For instance, in the example above, without the extra context, if you had 'Address' from User and Address from Created By user, you would have two same named Collumns of "Address (User)". Eventually, this is the solution our product group came to in order to prevent that issue.
To answer your original question, there is no means to change this behavior.
Thank you,Ken HubbardDynamics Support
Business Applications communities