Hello, I have been trying to modify a custom report which throws an error due to a multiselect list custom propery from test runs and have encountered a similar issue as described in the forum below: https://www.inflectra.com/Support/Forum/spirateam/reports/2265.aspx Ive reviewed the KB that was linked in the responses to the forum ( https://www.inflectra.com/Support/KnowledgeBase/KB638.aspx ) and have attempted to include the join and the Contains, EndsWith and StartsWith set of functions to the report query. The report is no longer throwing the error when generated, however it is only displaying the first value when multiple values are selected. The KB seems to describe creating a graph and Im wondering if since Im updating a report instead does the XSLT template require a modification as well to allow these values to display separated by commas? Here is the original query that was causing errors due to the custom property being a multiselect list: --pulling in the Environment information from the LOV left join (select SubC.CUSTOM_PROPERTY_VALUE_ID, SubC.NAME from SpiraTestEntities.R_CustomListValues as SubC where SubC.PROJECT_ID = ${ProjectId} and SubC.IS_DELETED = False) as CB on CAST(R.CUST_02 as INT32) = CB.CUSTOM_PROPERTY_VALUE_ID Here is what it was updated to: --pulling in the Environment information from the LOV left join (select SubC.CUSTOM_PROPERTY_VALUE_ID, SubC.NAME from SpiraTestEntities.R_CustomListValues as SubC where SubC.PROJECT_ID = ${ProjectId} and SubC.IS_DELETED = False) as CB on Contains(R.CUST_02, Concat(Concat(0, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String)), ,)) or EndsWith(R.CUST_02, Concat(0, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String))) or StartsWith(R.CUST_02, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String)) Also the XML code for the XSLT template for the value: Environment Thank you. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/reports/3158.aspxthreadId=3158Megan Robbins (megan.robbins@celerion.com) Hello, I have been trying to modify a custom report which throws an error due to a multiselect list custom propery from test runs and have encountered a similar issue as described in the forum below: https://www.inflectra.com/Support/Forum/spirateam/reports/2265.aspx Ive reviewed the KB that was linked in the responses to the forum ( https://www.inflectra.com/Support/KnowledgeBase/KB638.aspx ) and have attempted to include the join and the Contains, EndsWith and StartsWith set of functions to the report query. The report is no longer throwing the error when generated, however it is only displaying the first value when multiple values are selected. The KB seems to describe creating a graph and Im wondering if since Im updating a report instead does the XSLT template require a modification as well to allow these values to display separated by commas? Here is the original query that was causing errors due to the custom property being a multiselect list: --pulling in the Environment information from the LOV left join (select SubC.CUSTOM_PROPERTY_VALUE_ID, SubC.NAME from SpiraTestEntities.R_CustomListValues as SubC where SubC.PROJECT_ID = ${ProjectId} and SubC.IS_DELETED = False) as CB on CAST(R.CUST_02 as INT32) = CB.CUSTOM_PROPERTY_VALUE_ID Here is what it was updated to: --pulling in the Environment information from the LOV left join (select SubC.CUSTOM_PROPERTY_VALUE_ID, SubC.NAME from SpiraTestEntities.R_CustomListValues as SubC where SubC.PROJECT_ID = ${ProjectId} and SubC.IS_DELETED = False) as CB on Contains(R.CUST_02, Concat(Concat(0, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String)), ,)) or EndsWith(R.CUST_02, Concat(0, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String))) or StartsWith(R.CUST_02, CAST(CB.CUSTOM_PROPERTY_VALUE_ID as Edm.String)) Also the XML code for the XSLT template for the value: Environment Thank you. Fri, 16 Jan 2026 04:14:00 -05002026-04-15T09:56:19-04:00/Support/Forum/spirateam/reports/3158.aspxmessageId=7524Victoria D (nino.diasamidze@inflectra.com) Hello, Please check article KB726 - How to get the names of Custom List values instead of their IDs as it describes how to use JOIN with multiselect lists. I do not think XSLT requires a specific modification, it is more important for you to see the output in the preview first. Let us know if that helped. Regards, Victoria - Fri, 16 Jan 2026 10:46:41 -05002026-01-16T10:46:41-05:00/Support/Forum/spirateam/reports/3158.aspx#reply7524messageId=7525Megan Robbins (megan.robbins@celerion.com) Hello, Im able to successfully display only the first value that was selected from the test run multiselect custom property which uses a global custom list however additional values that are selected for the single multiselect list are not displaying in the report after using the Contains, EndsWith and StartsWith set of functions to the report query . Using the example from the KB linked in your response, if the project titled Billing System were to have two or more options selected for a single custom property such as having both Cat and Dog selected for the Pets custom property, would the query require additional modification to allow all of the options selected for the single custom property to display in the report? Thank you. Mon, 19 Jan 2026 02:02:31 -05002026-01-19T02:02:31-05:00/Support/Forum/spirateam/reports/3158.aspx#reply7525messageId=7526Victoria D (nino.diasamidze@inflectra.com) Hello, As described in KB726 , to display all the values (not only first), you need to use UNION function to get the rest if the properties displayed. If youre using SpiraPlan, then you can also check the article KB727 - Extracting Custom List value names using OData . In case youre still not able to get the values as desired, please share the full query so we can check exactly what you see. Regards, Victoria - Tue, 20 Jan 2026 09:39:32 -05002026-01-20T09:39:32-05:00/Support/Forum/spirateam/reports/3158.aspx#reply7526messageId=7597James Rivera (James271Rivera@outlook.com) Hello! Youre on the right track: the SQL join logic you added ensures the report query doesnt error out with multiselect custom properties, but the reason you only see the first value is that the reports XSLT template is still expecting a single string. In SpiraTeam, multiselect custom properties are stored as a comma‑separated list of IDs, and when you join to the LOV table youll only match one at a time unless you aggregate. Wed, 15 Apr 2026 09:56:19 -04002026-04-15T09:56:19-04:00/Support/Forum/spirateam/reports/3158.aspx#reply7597