cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Support Report to list all the values of the multivalued attribute in single row

Support Report to list all the values of the multivalued attribute in single row

Currently Query Builder Report is unnecessarily creating multiple rows for same business object if it's having attributes with multi values. Expectation is to keep single row with comma separated values as it does in details page of business object. It's unnecessary creating multiple rows where number of rows get manifold by number of such multi valued attribute and number of values each of attribute carries. It's redundacny of record and not in line with what information page/advance search page support. It's general expectation to get all multiple values together as current behaviour is not addressing any business scenario and it's creating confusion to end user where it's creating multiple permutations based on how many muti valued attribute exist and for each attribute how many values has been defined

 

Technical implementation is well understood on how the data is maintained in backend table and as a result why it’s coming as separate rows due to backend table. However it's not meeting any of end user business scenario where mutiple rows is expected based on multi valued attribute.

The expectation is inline with what details page and advanced search page supports and what a general expeecation exist in case of multi values attribute. Currently due to technical implemntation it's listing multiple rows

The current technical implemntation need to be updated to list all multi values in single row. As there is a customization which can list all mult valued attributes in single row ,  the same customization should be implemented as OOTB Implemntation . This will minimize the customization and maintenance cost of customer and moreover will support the most expected behaviour . Current behaviour doesn't seems fit for any business need and all customer need to support and make it appropriate by implementing customization. It would be better if it will be made part of product feature instead.

4 Comments
Marco_Tosin
20-Turquoise

This article could be helpful?

 

https://www.ptc.com/en/support/article/CS53268

bmr
17-Peridot
17-Peridot

@Marco_Tosin Thx. for the link, but as the case says, that's a workaround. 

abhishekjha
3-Visitor

Thanks @Marco_Tosin for your input. However this request is provide the feature as OOTB Implementation to avoid any customization and maintenance by customer. PTC has mentioned above link in there response. However current behavior is not supporting any business case and basic expectation is get all attribute values together instead of redundant rows with multile permutations .

aaronjlarson
11-Garnet

I fully support this idea, with one change.  When designing the Query Builder it should be a toggle option on the attribute within the select tab for the attribute if it is multi-value enabled.  Sometimes it is desirable to report separate records for each instance if you are pulling that result into another tool such as PowerBI.  Additionally I would suggest that you could choose your delimiter.  Sometimes you may want a comma and sometimes perhaps a semi-colon depending on what you are planning to do with the data once you return the report.  We do use the workaround today, but it is too unnecessary since the system can obviously already handle displaying in comma separated format.