By using this website, you agree to our Terms of Use (click here)
Good morning - I am newer to Acumatica and realize that there are some limitations on the ARM reporting tool. However, I cam across an import scenario for rows and columns. Has anybody ever used these or do they work?
Thanks,
They work beautifully. I find the ROW SET import most helpful. We have built new row formats is Excel and imported them into Acumatica. It usually required edits and adjustments but it is a quick way to load accounts or classes without having to hand enter each cell, one row at a time.
Also, this is the only way to copy a definition between tenants or sites.
Thanks Shawn! Have you ever completed the column layouts? I have a very complex report and it could be 100 columns.
@mark-kowalskil, the most complex I have done had about 40. If you are doing something with 100 columns, working in an excel spreadsheet might be helpful.
However, there is a difference between how column and row definitions are represented in Excel. Each row in a row format is represented as one row in Excel. However, with a column definition, I think there are 3 rows per column. To an extent, it makes sense if you think about the header portion of a column separate from the body of the definition. Still, a row format lends itself to editing and editing in mas more easily in Excel than a column. However, in Excel, you can see how each column compares to its neighbors more easily.
Good luck and keep us posted.
@shawn-p-slavin Would you be able to direct me to where I can find step-by-step directions covering how to format the excel spreadsheet to support importing into row or column sets?
I have never heard that was possible until I read your post.
Thank you.
@michael-peck I'm not sure there is a lot of published info on this. However, while in the ARM tool, you will find the export and import buttons in the same locations you are used to seeing them in Acumatica. I learned by exporting a ROW and COLUMN definition and then playing with the output in Excel. I then made a few minor tweaks in Excel and tried pulling the definition back into a new data set to see how it worked. I then did a larger test and eventually created definitions for specific reports where there were a lot of rows or columns involved.
If you find you have a really large report to work with, I think you will find Velixo to be an easier and more intuitive tool to use rather than fighting it in ARM.
Regarding moving ARM reports between Tenants, you can export and import the report on the Report Definitions (CR206000) screen. Included are the Row Set and Column Set that are attached to the report.
You can also package ARM reports into a Customization Project.
Does anyone by chance have an import/export scenario for Column sets they can upload the XML for?
Online Members
