aurelienclere-365/d365fo-cowork-plugin/d365fo-query-view

D365FO Query & View Discovery

Find and inspect reusable AxQuery and AxView definitions before building new data structures. Queries and views are the building blocks of reports, data entities, and form data sources.

When to use

• User is building a report or data entity and wants to reuse an existing query
• User wants to understand what a view exposes and how it joins its sources
• User is looking for the canonical D365FO query for a business concept

(e.g. "open vendor transactions", "posted sales orders")

• User wants to verify whether a view can serve as the basis for an OData entity

Workflow

1. Search for existing queries. Call search_queries(query) with business keywords

(e.g. "open purchase", "vendor trans", "ledger voucher").

1. Get query details. Call get_query(queryName) — returns data sources, ranges,

sorting, and the join structure.

1. Search for views. Call search_views(query) for materialised view objects.

1. Get view details. Call get_view(viewName) — returns the fields projected, the

underlying source query or table joins, and computed columns.

1. Recommend. If a query or view covers the user's need, present it as a reuse

candidate with an explanation of what it already provides vs. what would need extending. If nothing fits, describe the data sources needed for a new query/view.

Output Format

Query data sources

View fields

Notes

• D365FO views are indexed — they can be used in other queries and as data entity

sources. Prefer a view over a raw table join in data entities when the view already exists.

• Query ranges constrain what data is returned by default — check them before reusing

a query in a wider context (they may filter too aggressively for your use case).

• Standard query names follow the pattern <Module><BusinessConcept> (e.g.

VendTransOpenPerDate, PurchPurchaseOrderMaintain).