This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out.
Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved.
Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement.
Terms of Use |
Privacy Policy |
Trademarks |
Patents |
Contact Us
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).
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").
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.
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])