-
Notifications
You must be signed in to change notification settings - Fork 92
Description
## Describe the bug
Current behavior: the app can render photo thumbnails/previews from Dataverse image fields, but reliably getting full-resolution images inline is inconsistent/failing so far.
In our current implementation, thumbnail/preview images are shown using the image URL/value returned on the Dataverse record, and we fall back across available image representations (URL/data/base64) to ensure at least a preview renders.
## Steps to Reproduce
Go to the published app in web browser and open a record that has image fields populated in Dataverse.
Click a photo thumbnail to open the full-screen image preview.
The app attempts multiple full-image retrieval methods (Web API $value, @odata.mediaReadLink, Dataverse image download URL variants with Full=true, upgraded URL variants, cache-busting retries).
See that full-resolution image either does not load reliably inline, or falls back to thumbnail/raw preview quality.
Expected behavior
Clicking a thumbnail should consistently load and display the full-resolution Dataverse image inline in the app preview.
Actual behavior
Thumbnail/preview generally loads.
Full-size inline image loading is not possible, only seem to be able to access the thumbnail. Even when trying to load the .full image in the first instance for thumbnail.
Some candidate URLs return non-image responses, load failures, or lower-quality image results.
The app may fall back to non-full-resolution preview instead of true full-size output.
Screenshots or Error Messages
Environment information
Framework, build tool or relevant package used: React + Vite (TypeScript)
Any connection/components: Microsoft Dataverse (Power Platform / Code Apps runtime)
Additional context
Forcing Dataverse image download URLs to full mode (Full=true) and removing size constraints.
Trying multiple direct Dataverse image URL permutations (entity/attribute/id/timestamp variants).
Using Dataverse Web API binary endpoints ($value) with full/download query variants.
Requesting @odata.mediaReadLink and then loading upgraded/full variants from that link.
Retrying with cache-busting URL parameters and selecting the largest successful blob result.
Re-reading latest record image metadata and attempting full-image resolution again before fallback.
Any help very much appreciated! (Sorry if this is not actually a bug!?)