Forum Discussion
Text Filter has 100 characters limit in Power BI Service
Hello everyone,
I’m facing an unexpected behavior in Power BI Service related to text input length, and I’d like to know if this is a known limitation or a bug.
Scenario:
I’m working with a Microsoft Fabric Warehouse
I use a User Defined Function (UDF) to update comments in a table
From a Power BI report, users enter the comment using a Text Filter or text input
That value is then passed to the UDF to persist the comment in the Warehouse
Issue:
When the report is published to Power BI Service, the text input is limited to 100 characters.
The value arrives truncated to the UDF and is saved incomplete.
This does not happen in Power BI Desktop.
In Desktop, I can enter longer text and the UDF receives the full string.
What I’ve already checked:
Target column in the Warehouse is VARCHAR(MAX) or NVARCHAR(MAX)
The UDF supports long strings correctly
There is no truncation at the SQL or Fabric level
The issue seems specific to Power BI Service behavior
Questions:
Is there a known 100-character limitation for Text Filters or text inputs in Power BI Service?
Is this a Service-only limitation compared to Desktop?
Is there any way to configure or increase this limit?
Any recommended workaround for allowing long text input from reports?
Thanks in advance for any help.
Yes, Power BI Service limits text input to ~100 characters when using Text filter / text input–style interactions, even though Power BI Desktop does not. The limit cannot be configured or increased today.
As an alternative I belive you could use Power App visual but obviously you would need to work with Power Automate for that.
Hi jorgekino
The 100‑character cap in Power BI Service text filters is a documented limitation. While Power BI Desktop allows longer inputs, the Service environment truncates text filter entries at 100 characters. This restriction cannot be adjusted or expanded. To handle longer strings, consider alternative approaches such as parameters, embedding Power Apps, or leveraging custom visuals. Marketplace options like Text Filter Pro or Smart Filter Pro provide extended text input support beyond the default limit.
.
Regards,
Ritesh
Community Champion
Please mark the answer if helpful so that it can help others
Dance-Sing with Data -BI & Analytics
Hi,
A possible solution.
Enable “Accept multiple values.”
Change the comment variable from a str to a list.
Add code to format it into a readable sentence
comment = " ".join(comment)All other code can remain the same.
Use the comment variable as NVARCHAR(MAX).
Now, write sentences under 100 characters. Press Enter after each sentence.
4 Replies
- cengizhanarslan
Super User
Yes, Power BI Service limits text input to ~100 characters when using Text filter / text input–style interactions, even though Power BI Desktop does not. The limit cannot be configured or increased today.
As an alternative I belive you could use Power App visual but obviously you would need to work with Power Automate for that.
- ribisht17
Super User
Hi jorgekino
The 100‑character cap in Power BI Service text filters is a documented limitation. While Power BI Desktop allows longer inputs, the Service environment truncates text filter entries at 100 characters. This restriction cannot be adjusted or expanded. To handle longer strings, consider alternative approaches such as parameters, embedding Power Apps, or leveraging custom visuals. Marketplace options like Text Filter Pro or Smart Filter Pro provide extended text input support beyond the default limit.
.
Regards,
Ritesh
Community Champion
Please mark the answer if helpful so that it can help others
Dance-Sing with Data -BI & Analytics
- Dainius_AustynaNew Member
Hi,
A possible solution.
Enable “Accept multiple values.”
Change the comment variable from a str to a list.
Add code to format it into a readable sentence
comment = " ".join(comment)All other code can remain the same.
Use the comment variable as NVARCHAR(MAX).
Now, write sentences under 100 characters. Press Enter after each sentence.
- galaeciFrequent Visitor
This is not a valid solution!!
One of the key use cases for translytical functions was to allow users to enter comments. Limiting comment sizes to 100 characters is unaceptable.