Hi @travislawson ,

I typically keep the versions in Acumatica with a short description.  As well, I find that it is useful to save the rpx files externally as a backup, both the original and the modified versions.  I have not done so, but imagine that this could be done in a Github project.

A challenge that I have run into is when Acumatica makes a breaking change that affects a customized report.  One can always revert to the standard report, however changes need to be reapplied.  An example of this is the Inventory Balance Report (IN615000).  There were some significant breaking DAC changes in 2023 R2 that affected this report.  Customized versions of this report do not work after the update and have to be recreated.  Or the customized version has to be adjusted to account for the DAC changes.

It would be great to have a way to keep track of and reapply changes.

Laura

Yes!  I do the same thing.  I did add a textbox that’s not visible with a change log in the file so future modifiers can see it.  I did have the issue with the DAC changes breaking some reports also on the upgrade.  I’m doing my best not to modify them much from the “factory” due to this breakage. 

Certainly needs to be a different way.  I’m not a developer but Github seemed like a reasonable idea once I figure out how to use it.

We just did the 24R1 update and are slowly discovering that several reports are producing the #0 Error and we can’t see ANY versions of the reports.

The Inventory Balance report is one of the ones we aren’t able to view results on at all anymore.

How do you reset the report back to the default if you can’t get the report to pull up at all and access the VERSIONS?

Hi @brian11 ,

One way to get around this error would be to save a different valid rpx file as a new version (any report will do).  Once you are able to open the report edit screen in Acumatica, you can delete the new version that you just created and untick all of the version boxes to reset to the default.

Hope this helps!

Laura