BLOG
|
@hgaignard @BrettMartin1 - Thank you for reaching out on this issue! Because of the complexity of this update, there is a chance that there is something cached in the WebView2 and Cache folders in Power BI Desktop and in Power BI Online. This error when signing in is caused by the cache. Please run through the following steps to clear the cache. Reference: Clear the browser's local storage—ArcGIS for Microsoft 365 | Documentation On your local system, depending on how you installed Power BI, browse to one of the following folder locations: .exe version—%LocalAppData%\Microsoft\Power BI Desktop (for example, <user>\AppData\Local\Microsoft\Power BI Desktop) Microsoft Store version—C:\Users\<user>\Microsoft\Power BI Desktop Store App Delete the CEF folder. Delete the WebView2 folder. Delete the Cache folder. Restart your machine.
... View more
07-10-2024
11:20 AM
|
2
|
0
|
1436
|
POST
|
@Roland_at_Planet @nglchased - Thank you for reaching out about this issue. Would it be possible to post an animation (GIF) of this behavior? I am unable to reproduce this on my end using various and multiple data types. A follow-up question: are you both using the New modern tooltips option in Power BI? If so, those tooltips are not officially supported in our component as they are in a Preview state. Thank you!
... View more
07-10-2024
11:16 AM
|
0
|
1
|
748
|
POST
|
Hello everyone! I wanted to chime in on this topic since it has been open for quite some time. This isn't necessarily a bug (although it does appear that way in some cases). Because of technology restraints between our component and within Power BI, we have not been able to achieve this in the past. I know at the moment; it is quite cumbersome to make selections and not see the Legend or Table of Contents update. However, now that we have migrated to this new version, this particular topic is back on track for our project planning amongst the team. I will keep this thread updated and will post a blog once this has been updated/integrated. Please note that I do not have an estimated timeline for this. I know this is a very sought out feature to add to the component and have noted that in our project planning. Thank you everyone for your patience on this!
... View more
07-10-2024
11:13 AM
|
0
|
0
|
109
|
POST
|
Hello @Bloomers3166 ! Thank you for reaching out about this issue. I apologize for the inconvenience that this is causing. I had a look at this workflow, and I am unable to reproduce the issue on my end. I am using Enterprise versions 11.2 and 11.3 to attempt and reproduce it. Just to confirm: are you publishing the report or embedding the report? In a published scenario, there should be no sign in dialog whatsoever. In an embedded scenario, you will see a blocking page to sign in if the map contains private data. Lastly, what data is on the map? For my tests, I am using XY values, a public reference layer, and a private reference layer. Let's see if we can get this sorted out! Thank you!
... View more
07-09-2024
06:32 PM
|
0
|
0
|
1249
|
BLOG
|
ArcGIS for Power BI is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2024.1 (June/July 2024) update is a quality release. Performance improvements, UI/UX overhauls, bug fixes, design polishes, and quality of life updates have been made for the following features. Please make sure to update to the latest version of Power BI Desktop or refresh Power BI Online before upgrading. As always, please let us know of any improvements or issues you want to chat about! This version has started deploying in many regions. It may take up to three weeks to be deployed in all Power BI environments. ---- Reflection over the last year It has been quite some time since our last major release of ArcGIS for Power BI. Over the last year or so, we have been working hard to upgrade multiple areas of the component including bug fixes, user experience, performance, and many others. Now that we have fully migrated to a unified experience across the ArcGIS for Microsoft 365 components, we can provide regular updates in ArcGIS for Power BI. Getting to this point was a monumental task for the team and we hope that our work shines through. As a note, there are some new workflows and experiences that you will encounter. As with any major upgrade, our goal was to make sure that no previous work was lost as much as we could. When upgrading software, it can be tough to retain older components or workflows as technology advances at an exponential rate. That said, our work can only go so far. It’s you, the thousands of folks who use this daily, that make this work possible. Your ideas, bug reports, and feedback help us make the best possible software. This is a huge milestone for the team, and we hope you enjoy what we have done and all the future work that is coming! --- UI/UX Overhaul Across all the ArcGIS for Microsoft 365 components, our team has given each component a new, streamlined user interface and experience. The new interface makes use of Microsoft's Fluent 2 design library and places common widgets in the same location across all the components. We wanted this experience to be familiar whether you are working in ArcGIS for Power BI or in ArcGIS for Excel. You’ll see that menus can be resized, minimized, or removed completely. We’ve kept the teal theme to match the rest of the components in Power BI as well. Have a look and let us know what you think! Power BI Tooltips Over the course of this component’s life, it has been our goal to work as close to Power BI ecosystem as possible. A major pain-point in the ArcGIS for Power BI component has been the way we handle tooltips and pop-ups for the Power BI data layer. In this release, we have migrated to using Power BI’s tooltip framework. This also means that you can make use of report tooltips in ArcGIS for Power BI now. Keep in mind that there are differences between the versions of tooltips, however, the secondary goal of this change was to make sure that the map was no longer obscured. Further, tooltip annoyances such as windows popping up randomly or not over the correct feature have been addressed. This might change some of the workflows and the way your reports have been previously, but this was a necessary change to keep up with Power BI’s ecosystem and the usability of our component. Feature Information Now that we have moved to using Power BI’s native tooltip system, we needed to move the pop-ups from ArcGIS reference layers to a better location so that they wouldn’t obscure the map. For this, we’ve created a new Feature Information pane to display pop-ups from your ArcGIS layers. It can be toggled on or off from the Format pane. To learn more about the Feature Information pane and Tooltips, check out this fantastic article written by Na Zhang. Using Tooltip and ArcGIS technology to deep dive information in Power BI (esri.com) Join Layer The idea behind the Join Layer widget is to help you bring your spatial data from an ArcGIS layer and join it together with non-spatial data that lives inside your Power BI dataset. In this release, we have fixed a major pain-point when using the widget: the window must remain open when a join has been created. In this release, you can now perform actions with the window open, minimized, or closed completely. Give it a try and let us know what you think. We are going to be enhancing the Join Layer widget even further later this year. Take a look at the animation below. I am using a reference layer from ArcGIS and I am controlling the other visualizations on the report page. This is a joined layer and no longer requires the widget pane to be open. Legend Support We have added the ability to use a Legend in all the ArcGIS for Microsoft 365 components. You can add one or many layers to it, rename the legend, resize it, and even minimize it. We figured that this was a good starting point for the components as we have never had a true legend added to the map. We will be making enhancements to this widget in future releases this year and next. Bug fixes and polishes Now at this point, I would usually list out all of the bugs, UI/UX polishes, and quality of life updates made to the component. I can safely say that there are far too many to list in this release. As mentioned in many other posts on these forums, the goal of these fixes and UI/UX polishes is to make it easier to navigate and create meaningful maps for your report. Now that we have a unified experience across all ArcGIS for Microsoft 365 components, we would love to hear your feedback, whether it be an idea or if something is broken. Having open communication about the visual and how we can improve will keep us moving forward and paving the way for GIS in the Microsoft 365 ecosystem.
... View more
06-30-2024
12:01 AM
|
14
|
12
|
3514
|
POST
|
Excellent! I am glad we got it up and running! Good luck on your thesis and let me know if you need anything else!
... View more
06-27-2024
05:46 PM
|
2
|
0
|
765
|
POST
|
Hello @alvsigor and thank you for reaching out! I do apologize for the inconvenience that the new release has caused you. In our latest update, we have moved to using Power BI's native tooltip system and tooltips now follow that pattern. The only difference is if you are using pop-ups from a reference layer (this is where the new Feature information pane comes in). One way to solve this issue is to use the Report page tooltip function that is built into Power BI. Try the following steps and let me know if this solves it! In my example, I am using the following settings: 1. Create a new blank page in your Power BI report 2. You can hide this page in your report since it is being used for a tooltip 3. On the new blank page, navigate to the Format pane 4. Expand the Page information panel 5. Toggle on "Allow use as a tooltip" 6. You can name this page if you'd like to keep track of it 7. Under Canvas settings, select Custom from the dropdown menu 8. Adjust the canvas size based on your data. I am using 300x500px 9. On the report page, add two tables (or any other visualization that you want to use) 10. Add the appropriate data 11. Tab back to the report page that contains the map 12. Select the map on the report page 13. Navigate to the Format pane 14. Under the General tab, expand the Tooltips section 15. Select the new page that you just created 16. Hover over your feature and you should see the new tooltip displayed This also works for things like pie charts or any other visualization in Power BI.
... View more
06-27-2024
03:33 PM
|
4
|
3
|
788
|
IDEA
|
Good morning all! Thank you for your patience on this issue. As mentioned in previous posts, this was something that the team had been working on and we know had been a massive pain point for everyone (us included). I am happy to announce that the latest version of ArcGIS for Power BI has started its deployment process and should be rolled out to all regions over the next few weeks. One of the biggest changes outside of UI/UX enhancements, is the ability to use the Join Layer widget without having the window open. Take a look at the animation below. I can now make selections and filter the layer and Power BI data without the need to have the window open. We will be making additional enhancements to the Join Layer widget, but we thought this was a great start! Please let me know if you have any questions.
... View more
06-26-2024
09:12 AM
|
0
|
0
|
133
|
POST
|
@ISP_graynic - Thank you for reaching out and posting the screenshot. I might have seen this error before and it could be one of the following issues (potentially): 1. The Enterprise portal is rejecting the sign in from an "unauthorized" application. Ensure that the following redirect URLs are added to the application: urn:ietf:wg:oauth:2.0:oob
https://global.consent.azure-apim.net/redirect
https://global.consent.azure-apim.net/redirect/arcgisenterprise
https://global.consent.azure-apihub.us/redirect/arcgisenterprise 2. Is the Portal you are connecting to HTTP? Or are there any rules where HTTP is allowed? When setting up test portals, I noticed there were issues when the portal's security certificate was not valid. What version of ArcGIS Enterprise are you running?
... View more
06-11-2024
03:46 PM
|
1
|
5
|
284
|
POST
|
@ZachBodenner - Thank you for reaching out on this issue and posting a screenshot. Our documentation is slightly out of date as the deployment of the connector and our documentation is slightly out of sync. Can you add the following URLs to your Redirect URL list? Let me know if this solves it! https://global.consent.azure-apim.net/redirect/arcgisenterprise
https://global.consent.azure-apihub.us/redirect/arcgisenterprise
... View more
05-21-2024
12:32 PM
|
1
|
2
|
401
|
POST
|
Hi @RodPBI - thank you for reaching out on this topic. I know this is a massive pain point for you as well as many others including myself and the team. To give a bit of backstory on the way this feature works (at the moment), it was designed this way because of limitations within the infrastructure of Power BI and how we add reference layers to the map. When data is loaded from the data fields to a visual, a connection is made to let other visuals on the report page know that something is there or turned on. This is typical behavior in Power BI. However, when you add a reference layer to the map, the other visuals on the report page doesn't know it exists unless there is Power BI data associated with it. At the time of this feature being implemented, the only way to "trick" Power BI into thinking that the reference layer was a data layer, was to have the widget open. Some of the same rules apply to this method (in your first screenshot). In order for the report page to filter, Power BI data needs to be associated with the layer that you are selecting. I know this feature is quite troublesome. As mentioned in a previous post on the forums, the infrastructure in which we built this feature was incredibly restricting. However, we have this on our project board to resolve this year (post 2024 Esri User Conference). I do apologize as I know this has been a pain point for a long time. And I agree, having the window open is not ideal. However, it was (at the time) the only way to make Power BI know that data was on the map. Please bear with us as we now have a path forward to make this a better experience for everyone. Thank you for your patience on this issue!
... View more
03-07-2024
08:25 AM
|
0
|
0
|
534
|
POST
|
Hi @RobertAnderson3 ! Thank you for posting this. We have noticed a great deal of issues in the new CoPilot designer. This is also an issue we are aware of and notated it. We have an on-going list that we will be reporting to Microsoft. Please let me know if you run into any other odd behavior in the new designer as this is not controlled by our group.
... View more
02-22-2024
10:31 PM
|
2
|
1
|
381
|
POST
|
Hi @ScottLarkin and @AnneTetley - My apologies for not seeing this. Sometimes the posts in here get lost! I know this feature is quite troublesome. As mentioned in a previous post, the infrastructure in which we built this feature was incredibly restricting. However, we have this on our project board to resolve this year (post 2024 Esri User Conference). I do apologize as I know this has been a pain point for a long time. And I agree, having the window open is not ideal. However, it was (at the time) the only way to make Power BI know that data was on the map. Please bear with us as we now have a path forward to make this a better experience for everyone. Thank you for your patience on this issue!
... View more
02-22-2024
09:16 PM
|
3
|
1
|
531
|
POST
|
@JamesSheppardETM - Under further investigation, you actually do not have to pass in the custom geometry. In the Find Address Candidate action, you can use the auto-generated geometry output and pass it into the new record you want to create. Old designer: In the geometry field, click on the empty space, and then search for "geometry" in the Dynamic content pane. New designer: Click on the Insert expression icon. This will open the dynamic content pane. Then, under Dynamic content, search for "geometry".
... View more
02-14-2024
09:08 AM
|
0
|
0
|
352
|
POST
|
@JamesSheppardETM - Thank you for posting screenshots in your message. I think I see where the breakdown might be occurring. The geometry field should be formatted based on the following screenshot. In your post, it looks like you might have additional items in there. That said, we are working on some enhancements that will make it easier to create the geometry in a feature layer when it is being passed in from an external source. We are hoping to make so there won't be a need to manually write it out like below. I will keep you post on when that enhancement is ready!
... View more
02-13-2024
10:32 AM
|
0
|
1
|
383
|
Title | Kudos | Posted |
---|---|---|
1 | 06-11-2024 03:46 PM | |
2 | 09-04-2024 11:54 AM | |
1 | 08-27-2024 02:47 PM | |
5 | 08-15-2024 02:19 PM | |
1 | 08-15-2024 08:02 PM |
Online Status |
Offline
|
Date Last Visited |
09-05-2024
07:57 PM
|