By using this website, you agree to our Terms of Use (click here)
Notifications
Clear all
June 29, 2020 4:09 pm
Has anyone run into any issues when upgrading their report designer to the latest version and have successfully made changes on reports that run an older version of Acumatica?
Thanks
3 Replies
June 30, 2020 11:02 am
Report Designer is Build specific.
If you have upgraded used report designed on your pc.
You will need to uninstall it.
Once uninstalled.
Then download and install the correct build and install it.
http://acumatica-builds.s3.amazonaws.com/index.html?prefix%3D&source=gmail&ust=1593558285870000&usg=AFQjCNE6UbFJTH5a23z07V0fnEQ84Ee5h Q"> http://acumatica-builds.s3.amazonaws.com/index.html?prefix=
Or Go to the Acumatica portal and locate the build and download it
Logon to your instance and go to the problem report.
You need to have the report designer role.
If you can see edit you have the role.
Report, Edit report.
Then to diagnose the problem.
Go into Build Schema.
Then Reload the schema.
(What happens is reports have all the tables and variable that existed in the old version, as long as Acumatica has not
Removed a field, in most cases, the report will continue to function)
Once you Reload the schema the table - New fields may appear, old field s may disappear.)
You can look at the tables.
To see what is missing on the Tables, press Refactor.
This list orphan fields and gives you a chance to put the new field name.
You can also refresh it.
Next Check the Relationships. Sometimes Acumatica removes tables if that occurs
You will have the two tables, but the relationship for the table may be missing.
You can look at at other tabs and/or the actual report.
With builds if you are moving from 18.R1 to 20R1.
You should review release notes for 18R2/19R1/19R2 and 20R1.
As changes are only outlined once/
Regards
Matt
Matt
July 4, 2020 8:02 pm
Agreed that Report Designer is build specific, but I personally rarely run into issues when the versions don't match exactly.
July 6, 2020 11:02 am