To create a filter using comma separated field.

[Jayprekk]

Hi,

I need to pull data from a field (with comma separated values). This field continue to have new values added when new incidents are recorded into the DP table. I need it to be uniquely shown in the drop down list and be able to select multiple options. Based on my delection, it should filter the data from the DP table. I have added a image depicting this. I I have tried looking in the existing solutions but was unable to find the right solution.

[v-hashadapu]

Hi @Jayprekk , 

Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.

[Jayprekk]

Thank you for the help. Much appreciated

[v-hashadapu]

Hi @Jayprekk , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.

[Praful_Potphode]

Hi @Jayprekk ,

try sample PBIX and let me know.

Please give kudos or mark it as solution once confirmed.

Thanks and Regards,

Praful

[Jayprekk]

Thank you for the help. Much appreciated.

[amitchandak · Accepted solution]

@Jayprekk , I have made one attempt in the past as discussed in the blog 

Power BI- Text Part slicer to filter/search text - https://youtu.be/MKKWeOqFG4c
https://medium.com/@amitchandak/power-bi-search-text-parts-in-text-ad2f9783ffa2

[Jayprekk]

Thank you Amit for the wonderful video. As my dataset was big, this approach was the best for me. Thanks again. Apologies for the late reply as I was travelling. Thanks

[rohit1991]

Hii @Jayprekk 

Power BI cannot filter comma-separated values directly, so the correct solution is to split the tags into rows. In Power Query, use Split Column >> By Delimiter >> Comma >> Split into Rows to normalize the Security Tags field. This creates a proper one-tag-per-row table that you can use as a slicer. When the user selects “Bus,” Power BI will correctly return records like 1111 and 2222 because they now have a real relational match instead of text search.

[Jayprekk]

Thank you for the help. Much appreciated