Skip to main content
Solved

New reports throw 'Root Element is missing' after being published to Acumatica


plambert
Jr Varsity II

I am running into an issue when attempting to publish a new report I have created from scratch to my Acumatica instance. This is occurring after our upgrade to 24R2

Unlike the other related article, How to resolve the 'Root element is missing' error on opening a report in Acumatica Report Designer | Community, this error is happening in Acumatica and not the report designer itself. I know my report designer is working correctly because I can edit and save-to-server existing reports without issue.
The issue only happens when I try to use a new site mapping. I am able to connect the report designer to Acumatica. I can save it to the server. I have updated the Site Map screen to create a new screen for it - IN615300 since it is an inventory status report. I have set permissions to allow the appropriate people to access the report. Yet, when anyone goes to view the report, we all see: 

with a trace of: 

 

Is there some additional configuration I need for new reports? Are there restrictions to what names work for new reports or something else I have to set to be IN615300? Could this be caused by a version difference between the editor and Acumatica, which are 24.210 and 24.207 respectively? 

I’m at a loss for what could be going wrong; I appreciate any suggestions or new ideas!

Best answer by plambert

Frustratingly, it now works without my changing anything. I removed the entry in the site mapping, resaved the new report under a different name, started the process again from scratch, and can now view and run the report as expected. We did update recently, so perhaps something about that conversion was causing the error. I may have to re-publish the other custom reports, but thankfully that is not too large a task.

Thank you for your suggestions and insight, nonetheless!

View original
Did this topic help you find an answer to your question?

2 replies

WillH
Varsity II
Forum|alt.badge.img+1
  • Varsity II
  • 54 replies
  • March 27, 2025

@plambert 
If you log into your Acumatica site and go to the Tools screen you should be able to download the Report Designer installer for your Acumatica version?

Other products I deal with have similar errors because designers can open prior edition reports, but prior editions often can’t open reports designed in newer designers because of metadata not matching.

Alternatively, you could potentially open the .RPX file and compare it to a working .RPX file in a text editor to see if you can spot the difference in the report definition, but that’s so time consuming that if you’re able to use the correct report designer version you may find it quicker to do that and make the report again from scratch.


plambert
Jr Varsity II
  • Author
  • Jr Varsity II
  • 8 replies
  • Answer
  • March 27, 2025

Frustratingly, it now works without my changing anything. I removed the entry in the site mapping, resaved the new report under a different name, started the process again from scratch, and can now view and run the report as expected. We did update recently, so perhaps something about that conversion was causing the error. I may have to re-publish the other custom reports, but thankfully that is not too large a task.

Thank you for your suggestions and insight, nonetheless!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings