Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All 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