Recently I was trying to create a bunch of different views and I was using an existing view to "Save As" another view.
However, after publishing my new views, I would keep getting the error "Exception message: Table alias a_d8c7aa10e688e31180c200155d53e454 is not unique amongst all top-level table and join aliases" in the Event Viewer
When I looked into the FetchXml in SavedQueryBase table for the view that I just created, I would see that there were indeed two "linked entity
Searching the internet, I found mostly 2 dirty work around's and 1 perfect work around (perfect for me) to resolve this issue.
Dirty Work Around
1. Export the Solution with the entity inside it. Open the customization.xml and remove the duplicate reference to the "linked entity
2. Get the FetchXml for the view from the SavedQueryBase table and remove the duplicate reference to the "
Perfect Work Around (Perfect for my situation)
I just happened to accidentally read the comments left by one of the users in one of the blogs while researching a fix for this issue. I can't remember the blog or the commenter but all thanks to him for the issue resolution.
Root Cause
This is a bug in the product and apparently there was a fix released for this in CRM 2011 UR 12 but no fix has been released so far for CRM 2013 until UR 2.
The Root Cause is that if you already have columns from a "linked entity" in your "Entity Advanced Find View", any further views that you create that reference columns from a linked entity will throw an error.
Resolution
1. Go to the Entity Customization
2. Click on Views
3. Open the Entity Advanced Find View (Ex. Contact Advanced Find View)
4. Remove any references to columns that may have been added from another entity. i.e these fields do no exist inside the current entity.
5. Save and Publish the entity.
Thats it! Now, I was able to create all my views as usual without getting any errors. Hope this helps someone.
However, after publishing my new views, I would keep getting the error "Exception message: Table alias a_d8c7aa10e688e31180c200155d53e454 is not unique amongst all top-level table and join aliases" in the Event Viewer
When I looked into the FetchXml in SavedQueryBase table for the view that I just created, I would see that there were indeed two "linked entity
Searching the internet, I found mostly 2 dirty work around's and 1 perfect work around (perfect for me) to resolve this issue.
Dirty Work Around
1. Export the Solution with the entity inside it. Open the customization.xml and remove the duplicate reference to the "linked entity
2. Get the FetchXml for the view from the SavedQueryBase table and remove the duplicate reference to the "
Perfect Work Around (Perfect for my situation)
I just happened to accidentally read the comments left by one of the users in one of the blogs while researching a fix for this issue. I can't remember the blog or the commenter but all thanks to him for the issue resolution.
Root Cause
This is a bug in the product and apparently there was a fix released for this in CRM 2011 UR 12 but no fix has been released so far for CRM 2013 until UR 2.
The Root Cause is that if you already have columns from a "linked entity" in your "Entity Advanced Find View", any further views that you create that reference columns from a linked entity will throw an error.
Resolution
1. Go to the Entity Customization
2. Click on Views
3. Open the Entity Advanced Find View (Ex. Contact Advanced Find View)
4. Remove any references to columns that may have been added from another entity. i.e these fields do no exist inside the current entity.
5. Save and Publish the entity.
Thats it! Now, I was able to create all my views as usual without getting any errors. Hope this helps someone.
No comments:
Post a Comment