Forum Discussion
Azure Map Visuals Broken
We have a support ticket. They have acknowledged that this is an embed product issue, and a fix will be deployed by EOD on 9/23.
There is no indication as to what the fix is or any detail, but ideally, this gets resolved then. I hope this update helps others understand the timeline.
Hello,
We have the same issue in embedded (not in service) and I raised a support ticket to get help. It's affecting our customers and is quite annoying.
Then support came back to me with link to information that according to me is not relevant. He linked to this:
""
Overview for Microsoft Azure Maps | Microsoft Learn
Data Registry Service
Data is imperative for maps. Use the Data registry service to access geospatial data, used with spatial operations or image composition, previously uploaded to your Azure Storage. By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information, see Data registry in the Azure Maps REST API documentation.
Note: Azure Maps Data Service Retirement
The Azure Maps Data service (both v1 and v2) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps Data registry service by 9/16/24. For more information, see How to create data registry.""
I tried to explain to him that this is probably information that has to do with Azure Maps itself, not Azure maps in Power BI. We have no way of controlling where the Power BI Azure Maps gets its data from as far as I know. He still stood by his answer and I told him that it's not correct, I can't control the API calls and please escalate this to the MS Power BI Azure maps team.
He told me sure, and a few minutes later gave a messeage that:
"....Dear Alexander, as per our company policy, as we have provided the root cause of the issue, we will be reducing the severity of the service request to B. Rest assured, the issue will still be dealt with the utmost priority......"
Where I again told him he had not given me any solution.. Now I'm just waiting.
Did you get any other support/information? Or do you possibly get something from that information he gave me?
So ...
Anyone find a solution ?
Create the blob Azure Data Registry, ok, and after ? Microsoft don't provide an entire process for migrate ? JS lib no more valide and when you embed yours reports, with daily lot of users ... Web embedded front is broken ... I thought we found a robust solution ...How to upload data when blob data registry created ... Do we need to modify embedded code ...
Update:
The support has confirmed that they are working to fix this as soon as possible. So it's nothing we can fix and the above is as I presumed not relevant.
there is one intermediate "workaround" one can do that they gave me. I don't believe it's a good solution, but it might help someone else if you really need some page to work.
Use:await report.reload();
when report has rendered.
observe that this will reload the report but makes the map stable. However you'll have to code it to reload on first render but also whenever a change is made to, for example filters.We have a support ticket. They have acknowledged that this is an embed product issue, and a fix will be deployed by EOD on 9/23.
There is no indication as to what the fix is or any detail, but ideally, this gets resolved then. I hope this update helps others understand the timeline.Just checked one of my reports and looks to be resolved now
