Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Categories Visualization
Created by Guest
Created on Jun 24, 2016

More options in concatenate function

It would be useful to have control over how concatenation separates values rather than always using commas

  • Attach files
  • Guest
    Reply
    |
    Sep 22, 2020

    The original reason for this request was using Concatenate to summarise data from multiple rows - e.g. Concatenate([Column1]). Various workarounds are possible, but life would be much easier if it were possible to request concatenation with different delimiters. Using things like Substitute works OK as long as your data doesn't contain commas (although you can work around this by concatenating some sort of unprintable character at the end of the field before concatenating to aggregate and then substitute).

  • Guest
    Reply
    |
    Sep 22, 2020

    A workaround for this limitation is to add a "Calculate and Replace Column" transformation after the pivot to replace the default delimiter with the one your expect. The expression of the transformation should be something like Substitute([Test UniqueConcatenate], ", ", "\r\n").

  • Guest
    Reply
    |
    Jun 29, 2016

    I assumed the author was referring to the generation of a pivot table.  Currently, when concatenate is selected as the aggregation method when creating a pivot table, a comma is the only aggregation method. 

  • Guest
    Reply
    |
    Jun 29, 2016

    Can you please elaborate on this? it's not really clear to me what the request is or why would it be useful.

    Comma in the concatenation function is used to separate the function input, but then you can add extra separators in any way you wish to represent your data

    Eg: Concatenate([Column1],"-",[Column2])