New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap Text Not Working #334
Comments
Hi @c-sundahl, Could you send us an email at pbi.visuals@profitbase.com, and I'll see what we can do. Best regards |
has this been resolved? I encountered the same issue in my desktop file. Thanks, |
Hi @YuminYeah, It's fix is in progress now. One work around is actually going back to use v5.1 of the visual. It can be uploaded as an Organizational visual. -Anders |
Hi, this should be fixed in the latest version just released in beta now: See it here: https://github.com/Profitbase/PowerBI-visuals-FinancialReportingMatrix/releases/tag/v6.0.1-beta1 I would recommend trying it in Developer mode first. Details on how to turn that on here: -Anders |
Opened a dashboard I'm developing yesterday, and suddenly the wrap text behavior is not working for the Values variables. Until I opened it yesterday, the rows were expanding as desired to show the full string. The issue is occurring with both the current version I was working on and a prior back-up. It is affecting both my Desktop files and the files published to PBI service.
The only thing that changed was that I had done a data refresh from my source files. I've tried turning wrap text off/on, adding/removing variables, etc. but nothing is resolving it.
I'm using the matrix for an edge case where the values in the matrix are text based because your visual allows me to fix the width of the columns even though users will select different values to appear in the columns.
I am a civil service employee, but I have to log in here on my personal laptop/account as github is restricted on department computers. Also can't share the dashboard publicly yet. I am due to present this project in two weeks, so any assistance greatly appreciated.
The text was updated successfully, but these errors were encountered: