Industry and services
The ideal digital transformation partner is not only an expert in theory and technology but also in its customer’s industry. Our consultants are familiar with the processes, priorities and challenges of these eight focus industries.
Contact us
Manufacturing companies
proMX has long been focused on supporting manufacturing companies with their digital transformation.
proMX services
proMX helps you tackle challenges by analyzing your processes and customizing your system with tailored solutions. In our discovery workshop, we'll pinpoint the right tools to boost productivity. Let’s get started!
This might be useful
Partners
Partnering with proMX Group to offer the proMX 365 Productivity Suite provides a unique opportunity to enhance your business portfolio and drive significant growth.
Become a Partner
Our mission
All companies strive to digitalize and optimize their processes, and thus become more productive.
About us
proMX is your digitalization partner. Our goal is to help you transform your processes to make your business more agile, efficient and competitive. As a Microsoft Partner we are both extremely experienced and well-connected.
More about proMX
Our mission
All companies strive to digitalize and optimize their processes, and thus become more productive.
Frank Bursitzke
Apr 28, 2014 | Last updated: Dec 16, 2022
Expert articles | < 1 min read

If you have CRM 2011 and UR 15 you maybe know this error.

In your CRM organization you have added a custom entity and a system view for this entity. For the system view you have added one or more columns of an entity that is related to the custom entity (1:n).

You have created a custom report for the new custom entity, upload this report to the CRM, change the defaultfilter and save it.

If you try to execute the report, the execution fails with the following error on screen: “Reporting Error: The report cannot be displayed” and the following is logged in the platform traces.

Crm Exception: Message: Table alias <name> is not unique amongst all top-level table and join aliases.

Then you have an incorrect fetch XML in the defaultiflter of the custom report.

So to fix this there are two options:

  • Delete the report and upload it again
  • Directly update the FetchXML in the database

The second way is unsupported and only works for on-premises. But if you canot delete and re-import the report it might be the only way to solve the problem.