Ideas for Acumatica

Important! Please note that we do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive.
This portal is for product ideas and feedback only. If you need customer service assistance, please contact your Acumatica Support Partner or submit a support case.  You can also get assistance from community resources:  LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal. 

Idea for a new function called "Delimiter"

Add a new function to the Aggregates category of functions.

The new function would be called Delimiter and it would take two arguments: expr and delimiter

The function would take multiple rows and turn them into one row, putting the delmiter value in between each piece of data.

The expr value would be a field that could have more than one row in it (that's why the function would be in the Aggregates category)

The delimiter value would be the value that the user wants to put in between each piece of data. Most of the time this would probably be a space and a comma.

For Example:

Let's say we have a report that is grouped by sales order and one of those sales orders has four lines (1-4).

This formula:

Delimiter(SOLine.LineNbr,', ')

should return this:

1, 2, 3, 4

And this formula:

Delimiter(SOLine.LineNbr,' :: ')

should return this:

1 :: 2 :: 3 :: 4

So ', ' would probably be the most common delimiter used (not the space after the comma), but the function would allow the user to specify any delimiter that they want.

  • Tim Rodman
  • Jan 21 2015
  • Attach files
  • Gabriel Michaud commented
    January 21, 2015 03:50

    Interesting idea. For consistency with similar functions in VBScript and the .Net Framework, I would suggest to name it Join instead of Delimiter.

  • Tim Rodman commented
    January 21, 2015 04:42

    Sounds good to me. The name doesn't matter to me. The functionality is what I'm after.

    So many times I have been asked to put a field in a location where I know it could return more than one value. I end up doing something like displaying "more than one value" if MIN doesn't equal MAX just in case it happens in the data.

    Come to think of it, what do you think about adding a third and fourth parameter.

    Third: How many records would display before it stops and displays a custom message instead.


    Fourth: The custom message to display.

    This would prevent the field from growing out of control in case there happens to be a large number of values for a few of the records.