So I've been running into a clipping issue with my base64-converted images. Some images are too large, some have too much quality, and some are the wrong extension for the application, and I'm trying to find a happy medium, a ballpark estimate of number of pixels LxW to streamline the base64 conversion process. Right now I'm randomly resizing the image or lowering quality, probably a little too aggressively, and doing everything through trial and error, which is time consuming and laborious (for something that doesn't add that much value to my PBI for the time spent on it). What pixel length x width should I be ballparking my images to, to make sure the base64 fits in the power BI column and doesn't clip out? Is it something like 32 x 32 pixels, or am I approaching this completely the wrong way with resizing images?
Hi @guh950 ,
Please see if this document is helpful: Storing Large Images In Power BI Datasets Chris Webb's BI Blog
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I'm familiar with this article, although storing large images in a separate table with indexing would work, I'd have to rework my data modeling to do that, as I am currently using a dimension table with a unique key column that connects to other tables.
Join us for a free, hands-on Microsoft workshop led by women trainers for women where you will learn how to build a Dashboard in a Day!
User | Count |
---|---|
107 | |
74 | |
66 | |
50 | |
49 |
User | Count |
---|---|
163 | |
85 | |
76 | |
68 | |
67 |