New aggregate function in Generic Inquiries released in 25R2

Hello ​@jmorgan,

Could you please share the exact function you are asking about?

Yes sure.

Pg 180 of the release notes.

Platform: New Aggregate Function for Flexible Data
Presentation in Generic Inquiries
Acumatica ERP 2025 R2 introduces a new function for generic inquiries that outputs the aggregated records as a
single string. The new StringAgg function retrieves the values of individual records that comprise aggregated
data field and concatenates them into a single string. Thus, you can enhance the readability of your data inquiries.

​@jmorgan,

You can check this post, I think it is about the aggregate function you are asking.

Here we found a solution only by that line, there was no other way to get what was expected.

Thanks but that seems to be about grouping and using the count function.   I am referring to the specific aggregate function that is new in 25R2.

I dont have a query about using the function.  I just want to know why I would use it.

James

you are totally right, it is fully about having a line with aggregated values. It is like the Total row in Inventory summary, just have other available functions besides Sum.

Why to use? To get some totals in the gi itself without exporting to a report or excel. Thats just one purpose

Oh, I am a little sorry, I was talking about total aggregate function, the aggregate function just shows aggregated values in one column. The reason to use this is if you don’t have some total field on the record header like Sales order, and you need to calculate total from lines you just put it.it also allows to get Max, min and some other values. At the end it is just an aggregation, and as an example if you want to get total discounted discounted amount from the order you just sum it and show on the gi

Hi ​@jmorgan,
 

In Acumatica 2025 R2, the STRINGAGG aggregate function in Generic Inquiries allows multiple aggregated row values to be concatenated into a single string for display purposes.

This is useful when grouping data (for example, by OrderNbr or RefNbr) and you need visibility into underlying detail values—such as item IDs, descriptions, or amounts—without drilling into line-level records.

Typical business use cases include:

• Displaying multiple line-level values (such as item IDs, descriptions, or amounts) in a single row per document (Sales Order, Invoice, PO, etc.).

• Providing better summary views for users who want context without drilling into detail screens.

• Reducing the need for custom SQL views or code that were previously required to achieve similar output.