# Acumatica OData Generic Inquiry URL Builder

> Source: https://netray.co/tools/acumatica-odata-generic-inquiry-url-builder
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Generate the OData URL for an Acumatica generic inquiry, with $filter, $select, $orderby and $top, ready for Excel, Power BI or a script.

## Category

developer

## Erp

Acumatica

## Audience

- Acumatica developer
- BI analyst
- ERP administrator

## Tool

**Kind:** template

**Output:** code

**Language:** http

**Fields:**

#### Acumatica host

**Key:** host

**Type:** text

**Default:** https://mycompany.acumatica.com

#### Tenant name (OData v3 only)

**Key:** tenant

**Type:** text

**Default:** MyTenant

#### Generic inquiry name

**Key:** gi_name

**Type:** text

**Default:** OpenSalesOrders

**Help:** The name on the GI, with Expose via OData ticked.

#### OData version

**Key:** version

**Type:** select

**Options:**

- v3
- v4

**Default:** v3

#### Columns for $select (comma separated)

**Key:** select_cols

**Type:** text

**Default:** OrderNbr,CustomerID,OrderTotal,Status

#### $filter expression

**Key:** filter_expr

**Type:** text

**Default:** Status eq 'Open'

#### $orderby column

**Key:** order_col

**Type:** text

**Default:** OrderTotal desc

#### $top (row limit)

**Key:** top_n

**Type:** number

**Default:** 500

**Blocks:**

#### OData v3 endpoint (tenant in the path)

**Body:** GET {{host}}/odata/{{tenant}}/{{gi_name}}?$select={{select_cols}}&$filter={{filter_expr}}&$orderby={{order_col}}&$top={{top_n}}
Authorization: Basic <base64 of user@tenant:password>
Accept: application/json

#### OData v4 endpoint (selected with the version field above)

**Body:** GET {{host}}/odatav4/{{tenant}}/{{gi_name}}?$select={{select_cols}}&$filter={{filter_expr}}&$orderby={{order_col}}&$top={{top_n}}
Accept: application/json

#### Power BI or Excel feed URL

**Body:** {{host}}/odata/{{tenant}}/{{gi_name}}

**Notes:** Use the block that matches your version choice. Spaces and quotes in the filter must be URL-encoded when pasted into a raw HTTP client. The GI must have Expose via OData ticked on the Generic Inquiry screen, and column names are the GI result column names, not database fields. Confirm the exact path for your Acumatica build and whether your instance uses the v4 route.

## Content

**Intro:** Acumatica generic inquiries can be published as OData feeds, which is the usual route into Excel, Power BI and ad hoc scripts. This builder assembles the URL with the query options people usually forget to add.

**Sections:**

#### How to use the builder

**Body:** Enter your host, tenant and the name of the generic inquiry, then fill in only the query options you need. Copy the matching block into your client. In Excel use Data, Get Data, From OData Feed and paste the plain feed URL. Always limit columns with $select and rows with $top while testing, because a GI over transactions can return a very large result set.

**Bullets:**

- Tick Expose via OData on the inquiry first
- Test with a small $top before pulling everything
- Use a dedicated integration user with read access only

#### Filter syntax that works

**Body:** OData filters use operators such as eq, ne, gt, ge, lt, le and the logical words and, or. Strings use single quotes and dates must follow the format your OData version expects. Column names in $filter and $select must match the GI result column names exactly, including case in many clients. Complex joins and calculated columns belong inside the generic inquiry design, not in the URL.

#### Common mistakes

**Body:** The usual failures are a missing tenant segment, an inquiry that was never exposed, and a user without access to the underlying screens. A 401 means credentials or tenant, a 404 usually means the GI name or exposure. Remember that every OData call counts against your license limits on API usage, so schedule refreshes sensibly.

**Cta:** If your team keeps rebuilding the same inquiries for finance and planning, we can put a governed natural language layer on top of your ERP data. Ask us about a read-only pilot.

**Faq:**

#### Which Acumatica screen exposes a GI via OData?

**Answer:** Open the Generic Inquiry designer for the inquiry and tick Expose via OData in the header. Save it, and the inquiry becomes available as a feed under the OData endpoint for the tenant.

#### Should I use OData v3 or v4?

**Answer:** Both are available in current releases. v4 is the newer protocol and some clients prefer it, while many existing Power BI and Excel connections still use v3. Pick one per integration and keep it consistent.

#### Why does my filter return nothing?

**Answer:** Most often the column name or the value format does not match. Check the result column name in the GI, wrap text in single quotes, and test the filter without other options first.

#### Does this change data in Acumatica?

**Answer:** No. OData feeds from generic inquiries are read only. To create or update records you need the contract-based REST API or screen-based API instead.

## Search terms

acumatica odata url, acumatica generic inquiry odata, acumatica power bi odata, acumatica odata v4 filter, acumatica odata excel, acumatica expose via odata, acumatica odata query builder

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json