Acumatica grouped tables let users organize the results of one generic inquiry into expandable levels with detail rows, subtotals, and totals. In 2026 R2, the view can answer questions such as “which vendors drove this period’s bill total?” without building a separate Report Designer layout. A reliable rollout still starts with a correct inquiry, explicit access rights, aggregation checks, and a named reviewer. This guide explains the design and validation decisions for finance and operational teams; the documented feature requires the Grouped Table Views in Generic Inquiries feature to be enabled. Acumatica data-view overview.
Table of Contents
Enable the feature and confirm version
Select or repair the generic inquiry
Choose grouping levels deliberately
Configure groups, columns, and details
Distinguish personal, shared, and default views
Treat access to the inquiry as the first security boundary
Validate filters and period boundaries
Walk through a vendor-period example
Handle currency and mixed measures
Check performance and refresh expectations
Build a calculation specification
Verify the source inquiry’s row grain
Control shared-view publication
Test security with actual roles
Validate operational edge cases
Where Biz-Tech Services can help
What a grouped table changes
A grouped table is a representation of generic-inquiry results, not a new source of transactions. Acumatica says the same underlying inquiry can have a standard table, pivot table, and multiple grouped-table views. The inquiry’s parameters and filters still apply. A grouping can make a trend or subtotal easier to see, but it cannot correct a missing join, duplicated source row, wrong sign, or incomplete date filter. Start with the row-level inquiry and its business definition. Acumatica data-view overview.
Choose a question and grain
Write the exact question before configuring a view. “Bills by vendor and posting period” names a useful analysis, but the team must still decide whether each detail row represents a bill, bill line, adjustment, or payment. That grain determines whether summing Total Amount is legitimate. If a bill header is repeated for each line, a simple sum will overstate it. Define inclusions, statuses, currencies, branches, and a cutoff. Capture the expected row count and an independently calculated control total.
Enable the feature and confirm version
The 2026 R2 documentation says grouped-table representation requires the Grouped Table Views in Generic Inquiries feature on Enable/Disable Features (CS100000). Confirm that the target tenant and installed build provide it before designing a rollout. Acumatica’s reporting page describes nested groups, subtotals, and totals in 2026 R2; an older tenant may differ. Record the actual feature state and configuration instead of promising every user the same controls. Acumatica reporting overview.
Select or repair the generic inquiry
The view draws from one generic inquiry. If the desired fields currently live in several inquiries, Acumatica’s documentation says to create one inquiry containing the required data, then build the view on it. Review joins, parameters, filters, formulas, and row visibility with a business owner. Keep the inquiry’s detail output usable on its own. A grouped presentation is an analysis layer; it should not conceal bad source logic. Acumatica data-view overview.
Choose grouping levels deliberately
Acumatica’s tutorial groups Bills and Adjustments first by vendor, then by post period. That ordering answers a vendor-first question. Reverse the levels if the primary question is “what changed this period?” and then drill into vendors. Use keys that remain stable, such as a vendor identifier, rather than a display name alone when duplicate names are possible. Decide whether inactive or blank group values should appear as explicit exceptions. Acumatica grouped-table tutorial.
Configure groups, columns, and details
Acumatica documents two creation paths: group a column from inquiry results for a quick view, or choose Create View and type Grouped Table. In View Settings, configure each group’s fields, displayed columns, sort order, expansion state, and optional conditions. The Details section controls the underlying records. Put the identity and amount fields at the level where they are meaningful; a subtotal without a traceable detail set is difficult to review. Grouped-table configuration.
Select the right aggregate
Acumatica documents Sum, Average, Count, Distinct Count, Minimum, and Maximum among totals options. Choose the function that matches the business question. Sum amounts only after confirming the row grain and sign. Count records only when each record is the unit of interest; Distinct Count may be needed when a join repeats an entity. Average must specify its denominator and population. A visually plausible total can still be wrong when an excluded status, negative credit, or duplicate row was overlooked. Grouped-table configuration.
Distinguish personal, shared, and default views
Acumatica says a user with access to the generic inquiry can create a personal grouped-table view. Shared views require the role named in Security Preferences’ Personalization Management Role setting; a shared view is available to users who can access the inquiry. The documented tutorial also shows a shared Default View for All Users option for an administrator. Use a personal prototype first, then publish a reviewed shared view. A default change affects how others first encounter the inquiry, so test with their roles and daily tasks. Acumatica data-view overview.
Treat access to the inquiry as the first security boundary
A grouped view does not grant permission to its source inquiry. Review who can open the generic inquiry, which fields it exposes, and whether the user’s role should see the underlying records. Do not rely on a collapsed group to hide sensitive detail; users may expand it. Acumatica’s reporting guide separately documents access rights to generic inquiries. Test as representative roles, including the least-privileged reader and a shared-view editor. Acumatica inquiry access rights.
Validate filters and period boundaries
The inquiry’s parameters and filters apply to its data views. A period filter can make the same grouped view show a different total, so display and record the chosen period in review evidence. Test a period crossing fiscal year-end, late posting, reversals, and records lacking the expected grouping field. Reconcile each group to the detail rows and the overall total to an independently approved report. State whether the validation uses document date, post period, or another basis.
Walk through a vendor-period example
Suppose finance wants approved bill totals by vendor and post period. Begin with an inquiry that returns one row per relevant bill and includes vendor ID, vendor name, post period, status, currency, and signed amount. Filter to the approved population. Create a personal grouped view with vendor above post period. Display a sum and count at each period level, then inspect individual bills beneath it. Compare one vendor’s subtotal with the detail sum and compare the overall total with a separately generated control. The published Acumatica tutorial demonstrates vendor and post-period grouping; this validation design is an editorial example. Acumatica tutorial.
Handle currency and mixed measures
Do not sum unlike currencies into a single financial total unless the inquiry contains an approved base-currency amount and conversion basis. Likewise, do not combine quantities with different units or add order amounts to payment amounts without a defined measure. Group by currency or unit where necessary, and label calculated values clearly. This is a reporting-control recommendation; the documentation’s ability to aggregate does not determine an organization’s accounting policy.
Check performance and refresh expectations
A grouped table inherits the behavior and workload of its underlying inquiry. Acumatica separately describes generic-inquiry optimization that stores frequently used results in a data warehouse table and can refresh them on a schedule or on demand. That is a distinct feature with its own freshness tradeoff. If the inquiry is slow, inspect joins, filters, row volume, and the tenant’s supported optimization options before changing the view. Label any cached or refreshed result with its relevant timestamp. Acumatica reporting overview.
Govern changes after release
Name an inquiry owner, a view owner, and a business reviewer. Record the grouping question, source inquiry, filters, aggregates, expected control totals, roles, and change date. Revalidate when source fields, security, calculation rules, or Acumatica builds change. If a group suddenly disappears or total shifts, compare row-level source data before assuming the grouped view is broken. Preserve the prior view definition and test evidence until the new result is approved.
Build a calculation specification
For each displayed measure, state its source field, business meaning, unit, sign convention, aggregation, filters, and expected exceptions. “Total amount” is incomplete if users cannot tell whether it is document, base-currency, paid, open, or adjusted amount. For a vendor-period view, decide whether credit adjustments reduce the total, whether voided documents are excluded, and whether an unreleased bill appears. Write those choices in a short calculation specification and have finance approve it before comparing a grouped number to a ledger report.
Use a small set of known transactions to test the specification: one ordinary bill, one credit, one multi-line bill, one document posted in a later period, and one item in a different currency or branch. Calculate the expected group subtotal by hand from source rows. Then check the grouped table and the underlying inquiry. If the detail rows are wrong, repair the inquiry or source mapping. If the detail is right but the subtotal is wrong, inspect the aggregate and grouping field. This sequence isolates the defect.
Verify the source inquiry’s row grain
A generic inquiry can join header and line tables, or join a document to several related records. Such a join can repeat an amount even when every displayed row looks reasonable. Before summing a header amount, count how many rows each header produces. If it repeats, either choose a field at line grain, revise the inquiry, or use a calculation that explicitly accounts for the relationship. A Distinct Count of documents may be valid for a count question but cannot automatically repair a repeated monetary amount.
Test blank grouping keys and records that change groups after posting. A vendor name may change while its identifier remains stable; a period may be recalculated after a correction. If the same document can appear twice because of its relationships, show the source document ID in detail so the reviewer can detect it. Keep a reconciled export or query result for the acceptance test. The grouped view should make source logic clearer, not turn a join defect into a polished total.
Control shared-view publication
A personal view is a safe place to iterate. It lets the designer test hierarchy, column captions, sort order, and collapse state without changing the first screen other users see. Before sharing, review the view with people who use the inquiry for different tasks. A finance analyst may want vendor first; purchasing may want period or buyer first. Acumatica permits multiple grouped views based on one inquiry, so distinct questions can have distinct named views rather than one overloaded default. Acumatica data-view overview.
If a view becomes the default for all users, record who approved that change and how users can return to the standard table. Test the default with a representative high-volume inquiry and the ordinary reader’s role. A default that opens a collapsed hierarchy may help managers but hide the detail needed by an operator. The correct default is a usability decision, not a technical badge of completeness.
Test security with actual roles
Create a role test matrix before release. Include an administrator, a shared-view editor, a regular inquiry reader, and a user who should not access the inquiry. For each, record whether the inquiry opens, whether the grouped view appears, whether detail can be expanded, whether export is available, and whether personal or shared editing is allowed. Do not infer access from the designer’s session. A shared view being available to inquiry readers is not a reason to put sensitive columns into the source inquiry.
Review branch, company, financial, and field-level restrictions that apply in the tenant. Confirm the displayed subtotals reflect only records each reader is entitled to see. A manager’s total may differ from a branch user’s total because of access filters; label the scope instead of treating one as wrong. Where a total is meant to be organization-wide, approve the role and data policy explicitly. The view cannot compensate for an overly broad source inquiry.
Validate operational edge cases
Use test periods that contain a late posting, reversal, zero amount, negative amount, missing vendor or category, and a cross-period adjustment. Expand each suspicious group and trace the document IDs. Check whether an empty or null key creates its own group, disappears because of a filter, or is combined with another value. A disappeared exception can make a summary look better than the underlying process. Confirm that the overall total equals the sum of mutually exclusive groups under the same filter and role.
For averages, specify whether the denominator is detail rows, distinct documents, vendors, or periods. A vendor with one large bill and nine small bills has a different “average” depending on the chosen unit. Explain that unit in the column caption or accompanying note. For counts, decide whether zero-amount records and adjustments are included. These small definitions determine whether the grouped table supports a real decision.
Operate and maintain the view
Assign a person to review the source inquiry when a new field, customization, or integration changes the row set. Keep a baseline count and total for a known period so an upgrade can be compared to expected behavior. Check that shared and personal views still load, that default selections remain appropriate, and that role tests still pass. Do not update the acceptance baseline to match a new total until the changed source rows have been explained.
When performance degrades, capture the selected filters, row count, role, load time, and whether results are live or from a refreshed dataset. Optimize the source inquiry and its access pattern with a specialist before assuming that a different grouping order will solve the cost. If a scheduled dataset is introduced, state its last refresh time and decide which reports require current transactions. A fast but stale group total can be worse than a slower live result for close decisions.
Where Biz-Tech Services can help
Biz-Tech can review the business question, inspect the generic inquiry and role access, build a grouped view, and test its totals with finance or operations. The practical outcome is a view that makes a useful hierarchy visible while keeping the source rows and security boundary reviewable. See Biz-Tech’s Acumatica services and existing blog for related implementation guidance.
Conclusion
Start with one well-defined question and a verified generic inquiry. Create a personal grouped view, test its levels and totals against detail and an independent control, check access as real user roles, then publish it as a shared default only when the business owner signs off. The grouped presentation is valuable when its underlying records remain understandable and trustworthy.
Frequently Asked Questions
Is a grouped table a new report data source?
No. It is a representation of one generic inquiry’s results.
Does it require 2026 R2?
The cited documentation is for 2026 R2. Confirm availability and feature state in the target tenant.
Can an ordinary user make a personal view?
Acumatica says a user who can access the inquiry can create a personal view.
Who can publish a shared view?
The role identified in Security Preferences for personalization management controls shared-view creation.
Does collapsing a group hide sensitive records?
No. Control access to the inquiry and underlying data; test with actual roles.
Why might a sum be wrong?
Duplicated inquiry rows, mixed currencies, incorrect signs, or filters can distort it.
Can a view replace Report Designer?
It can cover some interactive hierarchical analysis, but complex formatted reports may still need another tool.
Can several grouped views use one inquiry?
Yes. Acumatica documents multiple grouped views based on the same underlying generic inquiry, each serving a distinct analysis question.
What should be checked before making a view the default?
Verify the inquiry’s row grain, aggregates, filter scope, role access, detail drilldown, and the effect on users who rely on the standard table.
Sources
- Acumatica grouped-table overview
- Acumatica grouped-table configuration
- Acumatica grouped-table tutorial
- Acumatica reporting overview
- Acumatica inquiry access rights
