Re: 64bit image

jdbmwl · ‎02-24-2025

I am currently using the Feb 2025 version of PBI and trying to get images to work in the Slicer

I have 2 different PIBX, one with just the imported images and one where I have data imported from a database that I want to link to
In the pbix with just the imported images (From sharepoint and converted to 64 bit), I can use the slicer and drop on the image name and then go to the visual settings under image and drop in the image field (it says First Image when I drop it in) and the image renders on the slicer
For the pbix that I really want this to work in, I link the image to a dimension table based on the name
in the slicer, I can drop on the name from one table, but when I go to the Visual configuration, under image, I drag over the Image column and nothing happens.
If I replace the name column with the image, the image will render just fine, but obviously the text under it is the 64 bit coding.
I cannot figure out why one pbix works and the other does not, AND, why the image will render in the name column, but the image field in the visual configuration does nothing?

rohit1991 · ‎02-24-2025

This is definitely a tricky one, especially with how Power BI handles images and slicers in recent builds. Based on everything described, here’s what I’d suggest for getting images working properly in a slicer:

Key points to check and try:

Data Categorization: You’ve already categorized your image column as “Image URL” (or possibly Binary), which is correct. Power BI relies on this categorization to know how to render the field.
Column Type: Power BI slicers don’t support rendering images when the field is a measure or a concatenated value, it has to be a column in your table, not a calculated measure or a long base64 string.
Length and Type of Base64 Data: Slicers (and visuals) can struggle if the base64 string is very large. If you’re using true base64 images (not URLs), sometimes Power BI hits a rendering limit and won’t show the image in the slicer’s “image” field, but might display it in the name/label field. For best compatibility, image URLs (even if to a local web server or SharePoint) are much more reliable than huge base64 blobs.
Try with a Sample Image URL: As a test, try replacing your image field with a plain HTTP/HTTPS image URL and see if the slicer image field works. If it does, the issue is definitely with the base64 or its length, not the slicer or Power BI version.
Consistency in Data Model: Make sure your relationships and data structure are consistent between the PBIX files. Sometimes importing data via SharePoint and converting it to 64-bit introduces invisible differences (encoding, line breaks, hidden metadata).
Known Bug or Limitation: There are some open issues in the Feb 2025 release regarding image rendering in slicers with certain data types and encoding. If you can’t get it working with a small base64 image or a URL, it might be worth trying the same model in a slightly earlier version of Power BI Desktop or submitting feedback to Microsoft via the Power BI Community or GitHub.

Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

jdbmwl · ‎02-25-2025

Thanks for the info, I did try to create an empty page and JUST work with the image name and image from the 1 imported table and same results. I did also confirm that I was importing and translating the same way between the 2 by taking the base 64 value of a couple of images and confirm they were created the same way. I was also using an older version and thought getting the latest would resolve, but that didn't work either. I will attempt to try and re-create as a calculated column.

jdbmwl · ‎02-25-2025

Interesting, creating a calculated column also didn't work. However, when I created a measure and had the image load in with a concatenatex(image field), THEN the UI allowed me to drop the field into the image spot on the slicer, but of course didn't render because it's too long.