Start

Home / References

Set up your toolsAbout 10 min, once

Get your data out of Acumatica

Last checked . Checked against Reporting dashboards and data analysis, GS how Export Data to Excel.html, GI Exposing Inquiry by Using OData Exposing Inquiry Through OData Activity.html, GI Access to Exposed Inquiry Through OData GeneralInfo.html, GI Access to Exposed Inquiry Through OData Data Retrieval.html, GI Access to Exposed Inquiry Through OData Excel Activity.html, RN Platform ODataPaths.html, Create a generic inquiry.

In short. In Acumatica, a Generic Inquiry (people say "GI") is a saved list of records, such as open sales lines. Anyone with access can open it and click Export to Excel. For a feed that refreshes on its own, IT turns on Expose via OData for that inquiry and gives you a read-only login.

Before you start

You need an Acumatica login and the name of the inquiry that holds the data you want. If nobody has built one yet, ask your Acumatica admin, or follow the "Make a new Generic Inquiry" part below if you have the rights, because building an inquiry takes some care with which tables it joins. These steps assume a current version (2024 R2 or later), and the Excel route works the same way in older versions. Exports hold prices and customer names, so read the safe use notes before any AI tool sees one.

There are two routes, and most people only need the first.

Route Who can do it What you get Good for
Export to Excel Anyone who can open the inquiry An .xlsx file, the same rows you see on screen A weekly dashboard or check you run yourself
OData feed IT turns it on once A web address that always returns today's rows A report that refreshes without a person exporting

Steps

Step 1. Open the inquiry

Type the inquiry's name in the search box at the top of Acumatica, for example "MR Open Sales Lines", and open it. If it does not show up, look for it in its workspace on the left menu (the ones that do not fit are under More Items), or ask your admin for its screen ID, because an inquiry only appears in search and menus after the admin publishes it.

Step 2. Set the filters you want

Fill in the boxes above the table, such as branch or date, and use any filter tabs the inquiry has. The export only holds the rows the table shows with those filters applied, so a forgotten filter means missing rows.

Step 3. Click Export to Excel

On the table toolbar, just above the column names, click Export to Excel. If you only see small icons, hover over each one until the tip says Export to Excel. Your browser downloads an .xlsx file. The column names are on row 1 and the records start on row 2. Depending on how the inquiry is set up, the file may also have a second sheet called Parameters that lists the filter values you used.

Step 4. Save it with the date in the name

Move the file into one folder you keep for this job, and rename it with the date you ran it, such as MR-Open-Sales-Lines-2026-11-16.xlsx. Keep every week's file, because each one is a record of what the ERP said that day.

Step 5. Do not fix it by hand

Leave the export the way it came out. If you need to look at it, open it and close it without saving. The scripts in our guides are built to read the export as Acumatica writes it, and a hand-fixed file is a different file every week.

Make a new Generic Inquiry

If the list you need does not exist yet, someone with rights to the Generic Inquiry form (screen ID SM208000) can build it. Open the form by typing "Generic Inquiry" in the search box at the top, or by choosing More Items in the Customization workspace. It helps to keep the Acumatica screen that holds your data open in a second browser tab, because you will need it to find the right tables. The steps below hold across versions, though the labels and the order of the tabs can differ a little.

  1. Start a new inquiry. Click the plus (+) button at the top of the form. Type a name in Inquiry Title, such as "MR Open Sales Lines", and press Tab. The OData address ends with the inquiry's name, so pick one that is short and clear. The Site Map Title is the name people see in menus and search once the inquiry is published.
  2. Find the tables. A document such as a sales order keeps its top part (order type, number, status, customer) in one table and its lines (item, warehouse, quantity) in another. To learn a table name, open the document screen, click Customization in the top bar, choose Inspect Element, and click a field. The Element Properties window shows the Data Class, which is the table name. For the Order Type field on Sales Orders it shows SOOrder. Write down the table for every field you want. Inspect Element needs customization rights, so your admin may need to do this part. If a table you expect is missing from the list in the next step, ask your admin, because developers can hide tables from inquiries.
  3. Add the tables on the Data Sources tab. This is the first tab of a new inquiry. Add a row, type the table name in the search box of the pop-up, pick the table, and repeat for each table you need.
  4. Join them on the Relations tab. When you use more than one table, you tell Acumatica how their rows line up, usually by matching the order type and order number. A wrong join is the usual reason for the same line showing up twice, so check for repeats after you save.
  5. Add Parameters and Conditions. Parameters are the boxes people fill in at the top of the inquiry, such as branch or date. Conditions are rules that always apply, such as "status is Open". The Grouping and Sort Order tabs are optional.
  6. Choose columns on the Results Grid tab. Pick the fields you want and put them in the order you want. Their headings become the column names in the Excel export, and the OData feed carries the same columns, so leave out cost and personal fields the report does not need.
  7. Save, then check it. Save the inquiry, open it, and compare the first rows with the same records on the original screen. Fix the join or the conditions until they match.
  8. Publish it, and expose it if you want a feed. Fill in the Screen ID so the inquiry is published, and give the roles that need it rights to the new screen. For a feed, select Expose via OData and save again. Acumatica's help puts that check box on the Interface Options tab, and a tutorial for the form lists different tabs, so if you do not see that tab, look for the check box by name.

The OData route (ask IT)

OData is a standard way for a program to ask for a list of records over the web, like asking for the same export without clicking. (What is an API? explains the idea.) For an inquiry, it works like this: an admin opens the inquiry on the Generic Inquiry form (screen ID SM208000), selects the Expose via OData check box (Acumatica's help places it on the Interface Options tab), and saves. The inquiry must be published (it has a Screen ID) for this to work. After that, the inquiry's rows are available at a web address, and only to a login that has rights to that inquiry.

You can send IT this request, with your own inquiry name in it.

Subject: Read-only OData feed for one Acumatica inquiry

Hi,

I would like to read the Generic Inquiry "MR Open Sales Lines" through OData, so a report can refresh without a manual export each week.

Please:
1. Select the Expose via OData check box for this inquiry on the Generic Inquiry form (SM208000).
2. Create a separate user for the report with a role that has View Only rights to this inquiry, and no other screens.
3. Send me the OData address for the inquiry and the tenant name.

The report only reads data. It does not create or change anything in Acumatica.

Thank you.

IT will send back an address in one of two shapes. Since version 2024 R2 it looks like https://<your-acumatica-address>/t/<TenantName>/api/odata/gi/<InquiryName>. Older versions use https://<your-acumatica-address>/odata/<TenantName>/<InquiryName>, which still works for a while after an upgrade. Adding /$metadata to the end of the .../api/odata/gi part lists every field the feed has.

To check the feed yourself, open Excel and choose Data, then Get Data, then From Other Sources, then From OData Feed. Paste the address, choose Basic, and sign in with the report user's name and password. Type the user name alone, without the tenant name after it. Excel shows the inquiries that login can see, and you pick yours and click Load.

The feed has the same rows as the export, but the column names are shorter. The OData names have no spaces or dots, so "Open Qty." in the export usually shows up as "OpenQty" in the feed, and dates come with a time and time zone on the end. A script that maps columns by name once, like the one in Build a weekly dashboard from an Acumatica inquiry, only needs its column map changed to read the feed.

Acumatica also has a contract-based REST API, which programmers use to connect other systems. It runs the same business logic as the screens, so it is built for exchanging and changing records, not only reading them. For a report that only needs to read a list, the OData feed is the simpler and safer request.

Keep the feed safe

  • One user, one job. The report's login can view only the inquiries it needs, so a leaked password exposes one list, not the ERP.
  • Never paste the password into an AI chat. Keep it in a password manager or in the tool IT sets up.
  • Use the https address. Acumatica's own docs strongly recommend HTTPS, because the basic sign-in sends the user name and password with each request.
  • Pick fields with care. The feed sends every column in the inquiry. Ask the admin to leave out costs, margins, or personal details the report does not need.
  • Know who can see the list. Any signed-in user can see the list of exposed inquiries, though they only get the rows their rights allow.

Check it worked

Open the exported file and close it without saving. Row 1 should hold the column names you saw on screen, and the first and last records should match the first and last rows of the table in Acumatica. For the OData route, Excel's Navigator should list your inquiry and load the same rows.

If something goes wrong

  • Export to Excel is grey or missing. Your role may not have rights to export from that inquiry, so ask your admin, who controls it in the inquiry's access rights.
  • The export fails when you have typed in the search box. Some versions had trouble with search-box filters on export. Clear the search box and use the inquiry's filter boxes instead, or put an asterisk on each side of the search words.
  • Dates come out as "11/20/2026 12:00 AM", as text. That column is a formula in the inquiry. The scripts in our guides handle it, and your admin can bind the column to the date field itself so Excel gets a plain date.
  • Dates are one day early. Date and time fields show in each user's time zone. Check your time zone in your user profile, and ask the admin to use a date-only field.
  • The OData address says not found. The tenant name must match the company login name exactly, and the inquiry name must be the inquiry's own name, so ask IT to check both.

Used in

Get your first win this week.

One minute. Three guides picked for your job.

Start my first win