Select to view content in your preferred language

ArcGIS Maps for Power BI v2024.1.400 completely broken

1819
5
08-26-2024 09:36 AM
Labels (2)
Ku3i6RyEQAkzv
Occasional Contributor

edit: It turns out Map Tools > Settings > Validate is not a new feature. I just had never seen or used it before. My report has had a public link/embed code for months with functioning ArcGIS visuals, so the Validate step is probably not causing the problem.

---

I have a Power BI report using the ArcGIS Maps for Power BI visual that has existed for several months. This visual is used on two pages: the home/landing page and one other page. The June/July v2024.1 update caused some headaches, but I rebuilt the visuals, and they have been working since then.

Last Friday (Aug 23, 2024), the visual on the second page started saying, “This map does not meet the requirements for published reports.” This was confusing, because the structure of the visual had not changed since I rebuilt it after the v2024.1 update.

This morning, I opened the report in Power BI Desktop to troubleshoot, and I found that both visuals (not just the second one) appeared blank other than their titles. I refreshed the data, and nothing happened. And I could not access the Map Tools because the maps don’t appear.

I tried adding a new page and creating a new map from scratch. While doing this, I noticed several changes to the Map Tools experience. Regardless, I took the following steps to investigate.

  1. Add latitude and longitude from a Power BI table into the latitude and longitude fields
  2. Add a layer from my enterprise ArcGIS data by going to Map Tools > Layers > ArcGIS Data > ArcGIS > My Groups > ABC Group > DEF Layer
  3. I first noticed a problem when the Coordinates layer did not appear where it used to under Map Tools > Layers. Only the DEF Layer appeared. The coordinates also didn’t appear on the map.
  4. I scrapped this map and restarted again. This time, I only added the lat/long fields and did not bother yet with the ArcGIS layer.
  5. Again, the Coordinates layer did not appear under Map Tools > Layers. Neither did they appear on the actual map.
  6. I repeated these steps to create another new map after signing out of ArcGIS through the tool and instead choosing Continue as Guest. I got the same results.
  7. In my troubleshooting, I noticed something new under Map Tools > Settings > Settings. It read, “Embed and publish to web: Check to make sure your map will publish and embed without failures.” And beneath it was a button reading Validate.
  8. I created another new map and signed into ArcGIS and added lat/long (the same steps I took in Step 4). Again, I had to do this on a new map because the Map Tools are not accessible on my existing maps. They still appear blank.
  9. I clicked the Validate button. Then, in a green box, it said, “The map has passed the embed and publish check.” It also displayed 4 green checkmarks for Coordinates, Basemap Layer, Reference Layer, and Infographic Cards.
  10. The coordinates then appeared on the map, and a Coordinates layer appeared under Map Tools > Layers.
  11. I repeated the validation step after creating another new map, this time with both the lat/long coordinates and a layer from my ArcGIS data (like in Steps 1 and 2).
  12. The coordinates appeared on the map, and both the Coordinates layer and DEF Layer from ArcGIS appeared under Map Tools > Layers.
  13. I switched back to the pages with my existing visuals, hoping the validation would somehow carry through all the map visuals, but they still appeared blank.
  14. When I switched back to the page with the new map, that map now appeared blank as well.
  15. To reiterate, these maps appeared blank with no error message. The only error message was displaying on the second visual when viewed through the public link, saying, “This map does not meet the requirements for published reports.” Which is clearly incorrect because the visuals were validated.
  16. At this point, I had the thought to try these steps again the Power BI Service editor instead of Power BI Desktop.
  17. I created a new page with a new report with the lat/long coordinates and the DEF Layer.
  18. This time, when I switched back to the pages with the other two visuals, they worked! The new map visual also worked when I went back to that page!
  19. I deleted the new page and visual, and the other two continued to work.
  20. I saved and closed the report.
  21. I opened it in a new tab through the workspace link (not the public link). The map on the home/landing page appeared blank, but when I navigated to the page with the second visual, it worked! Then when I went back to the Home/Landing page, that visual worked as well. I figured I had found a barely passable short-term solution.
  22. I opened the report from the public link and was greeted by a functioning visual on the home/landing page!
  23. I navigated to the other page, and that visual was still broken. It was still returning the message, “This map does not meet the requirements for published reports.”

During my troubleshooting, I re-read Esri’s and Microsoft’s documentation for setting up the ArcGIS Maps for Power BI visual. Neither gave me any other ideas. Esri’s documentation appears to have been updated to reflect the “Embed and publish check” under Settings. Microsoft’s documentation (https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualizations-arcgis) hasn’t been updated to reflect the v2024.1 update. In fact, it hasn’t even been updated since Apr 19, 2023. Even some of their links to Esri’s site are broken (https://www.esri.com/powerbi).

I checked the ArcGIS for Power BI Blog on the Esri Community site where the post for v2024.1 (https://community.esri.com/t5/arcgis-for-power-bi-blog/arcgis-for-power-bi-v2024-1/ba-p/1499563) was published. I looked for a similar post for v2024.1.400, but one does not exist. I looked all over for patch notes and could not find anything.

I am at a loss and out of ideas. My organization just debuted this report to our board and to the public on Thursday, and the maps (one of the critical pieces) stopped functioning literally the next day.

If someone asked me to summarize my experience using this visual in one word (even before this occurred), I would describe it as “frustrating.” I would also tell them to consider it a preview tool in beta and not an officially released product. I’ve spent more time working against this tool than working with it. However, before Friday, it was at least functional.

Both Microsoft and Esri employ thousands of people. And yet, neither can be bothered to follow basic software release procedures and publish patch notes. To me, this speaks to the lack of professionalism with which this tool is treated.

I’m sure the developers are working hard to maintain and update this tool, but the casualness of QA (again, even before this situation) and indifference to proper documentation make me regret using it and will have me recommending others not even try it for a long time.

Frankly, it is unacceptable to release a so obviously undercooked and broken product without calling it a beta.

Anyway, does anyone here have ideas on how to fix this?

5 Replies
NickLudowese
New Contributor

I had much the same problem. I narrowed it down to having labels enabled for a polygon feature class in a map. I disabled the labels in the map on arcgis online, reloaded the map into Power BI Desktop, republished to Power BI service and it worked. Not a great fix since I no longer have labels on my polygons.

0 Kudos
Ku3i6RyEQAkzv
Occasional Contributor

Unfortunately, my problem is occurring even before bringing in any layers from ArcGIS. It happens even when all I add are lat/long from a data table in Power BI.

0 Kudos
Ku3i6RyEQAkzv
Occasional Contributor

It turns out Map Tools > Settings > Validate is not a new feature. I just had never seen or used it before. My report has had a public link/embed code for months with functioning ArcGIS visuals, so the Validate step is probably not causing the problem.

0 Kudos
BradyChristianson
New Contributor

Did you ever figure out a solution to this?  I'm having the same problem.

 

I find that sometimes if I remove a tooltip then re-add it, it will make the map work again. 

0 Kudos
Ku3i6RyEQAkzv
Occasional Contributor

@BradyChristianson The visual is broken. Esri's support team confirmed it. I'm baffled they released an update that broke this product. They won't be able to fix the bugs until November at the earliest because publishing to Microsoft requires various approvals and takes time. Here is a community post from someone at Esri.

ArcGIS for Power BI - Maps not loading properly issue update - Esri Community

After this experience, I strongly recommend not using this visual. If they treat it this casually and release updates without properly testing them, who's to say they won't do it again in the future?

They helped me find workarounds that almost resolve the issues in the meantime, so I give their support team some credit.

  1. In Power BI Desktop, like you mentioned, you can get it to function again by toggling something in the Visualizations > Format Visual panel, but you have to do this every time to open the file or switch to a different page. You can resolve the issue by deleting your map visuals, clearing your cache, and rebuilding them from scratch. They instructed me to clear the cache by going to C:\Users\[your user]\AppData\Local\Microsoft\Power BI Desktop\ and deleting the Cache and WebView2 folders.
  2. In the Power BI Service, for internally published reports, there is no true resolution. If there is a map on your landing page, it will not load. But if you go to another page and then go back to that page, it will load. Sure, this is just one extra step for me, but telling your end users the map doesn't work unless you flip back and forth between pages isn't a great look.
  3. In the Power BI Service, for public/embedded reports, if you clear your cache, rebuild the reports from scratch, and republish the report, the maps will work.

I started testing the Azure Maps visual and may transition to it entirely. It has several limitations, so you have to weigh the pros and cons. But so far, it seems more reliable. Even before this, I felt like I was constantly fighting the ArcGIS visual to force it to work as expected. That has been less so with Azure Maps. I suspect the Azure Maps visual gets more regular attention from Microsoft than the ArcGIS visual gets from Esri. We shall see.

0 Kudos