Customizing User Inputs in the Text Slicer Visual on PBI Desktop

[Uttasarga]

Hi Fellow PBI'xers, I've a report that has a Text Slicer Visual (Preview Feature), in which what I want to do is lpad default "0000"  to the user's input, until the point where the input string is 14 Digits in Length.

Example - If the user inputs "1234567", then the text slicer should add leading zeros to this input, thus making it "00000001234567".

[v-nmadadi-msft]

Hi @Uttasarga ,

Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.

Thank you for being part of the Microsoft Fabric Community.

[Uttasarga]

@v-nmadadi-msft  -  Is there a way where I can write a UDF for this?

[v-nmadadi-msft]

Hi  @Uttasarga ,
Thanks for reaching out to the Microsoft fabric community forum.

Using UDF is similar to the approach I have provided earlier, The output of the UDF will be creation of 123456 as a separate column which as you mentioned is not suitable for the setup you are currently using.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[v-nmadadi-msft]

Hi @Uttasarga  ,
Thanks for reaching out to the Microsoft fabric community forum.

A workaround for what you are trying to achieve is by using Duplicate column in transform data

With that duplicated column, you can split the column by based on number of characters

Now you will get 1234567 as a separate column, you can directly enter it into the input to filter the visuals of your choice.


If this post helps, then please consider Accepting as solution to help the other members find it more quickly and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thank you

[Uttasarga]

Hi @v-nmadadi-msft , but that would mean to remove leading zeros from the column values.
My report is using Direct Query, and the data volume is 8M rows on avg, each day since the past 4 years. Doing a customization you mentioned above will not be supported by Direct Query.

[v-nmadadi-msft]

Hi  @Uttasarga ,

The Text Slicer itself does not support transforming input. It takes the user's typed value exactly as-is and tries to match it with what's in the column used in the slicer. If the provided workaround does not match your requirements and
If the feature is important for your functionality Please consider sharing your suggestion in the Power BI Ideas forum
 Fabric Ideas - Microsoft Fabric Community,
where the product team actively monitors user feedback. Ideas with strong community support are more likely to be considered for future implementation. Posting there helps ensure your request reaches the right audience and contributes to shaping the product roadmap.

Thank you

[lbendlin]

Why not do the padding in the UDF?

[Uttasarga]

Hey @lbendlin , so I should create a UDF that does the padding of user inputs in the text slicer?

[lbendlin]

That would be my suggestion. Where are you planning to store the user input?

[Uttasarga]

Do you have an example I can use? User's Input will be in a Text Slicer Visual