topic Custom Visual Blank until a data update in Custom Visuals Development Discussion

Custom Visual Blank until a data update

_JamesB — Thu, 28 Mar 2024 13:41:32 GMT

Hi There,

I have a custom visual that I am developing that shows a strange issue that I can't seem to find mentioned anywhere else. When I put the visual onto a page and populate it with some data in the visualisations pane it displays exactly as I'm expecting. However, if I navigate away from that page and back to it the visual is now blank until I give it an update of some kind. This can be either changing the value of a slicer on that page or by ammending the data given to the visual in the visualisations pane.

If I load up the visual through the developer visual this behaviour also persists. Any change I make to the code triggers a refresh which causes the visual to go blank until either of the aformentioned data updates.

Has anyone seen this issue before? I feel like it could be related to an update in the powerbi-visuals-api since I first built this visual at which time it didn't display this behaviour but can't find anything about it!

Thanks,

James

Re: Custom Visual Blank until a data update

dm-p — Sun, 31 Mar 2024 04:28:37 GMT

Hi @_JamesB,

It seems to be an issue with the developer visual affecting a few of us. It's not intended functionality and seems to be a recently introduced issue, but when you package your visual, it will work as expected.

Your best bet is to follow up with MS directly, as the custom visuals team does not monitor the forums - their support address is pbicvsupport@microsoft.com.

Regards,

Daniel

Re: Custom Visual Blank until a data update

_JamesB — Tue, 02 Apr 2024 10:05:13 GMT

Hi @dm-p ,

Thanks for the response! Unfortunately the issue is present in the packaged up version - I went into the developer visual to see if I could isolate where it was coming from but to no avail. I guess I could try building it from the ground up again...

I will also drop the MS team a note in case they are able to give any pointers.

Thanks,

James