Latest Contributions by AnthonyLatini

ArcGIS for Power BI is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2022.4 (December 16th, 2022) update is a quality release. Performance improvements and bug fixes have been made for the following features.  If you do not see the changes, you may need to close out and restart Power BI Desktop or restart your browser if you are using Power BI Online.  As always, please let us know of any improvements or issues you want to chat about! ---- Drive time The Drive time widget has gotten a bit of an upgrade with this release. In this release, a user that is logged into an ArcGIS account will see several new options available when creating a drive time buffer. This enhancement mirrors a great deal of the features available in ArcGIS for SharePoint and ArcGIS for Excel. There are some slight differences between ArcGIS for Power BI’s component, SharePoint and Excel's, however, most of the core features are there. For example, you cannot share the buffer you created to ArcGIS Online or Enterprise. As a note, there have been no changes for Standard users with Drive time. To see the full suite of changes, you must be signed into an ArcGIS account. Above: Drive time - ArcGIS for Power BI v2022.4.117   Drill-through support ArcGIS for Power BI is now supported when using the drill-through field wells in Power BI. Once you set up your target page and fields, you can right-click on a feature and drill-through to other pages in your report. Give it a try and let us know what you think!     PKI and IWA Support For a long time, authentication methods were somewhat limited in Power BI Desktop and Power BI Online. However, due to some recent changes in the infrastructure of Power BI Desktop, you can now authenticate using PKI or IWA methods. All other previous methods of signing in are still supported.    ---- Bug fixes and polishes galore! In this release, we have squashed a ton of bugs and polished a great deal of the visual. Here is a small subset of the items we tackled between our last release and this one. Nearing the end of the year and we are already working on another release for January 2023! Bug fixes: Fixed an issue when using the 'Reset to default' option in the Formatting Pane of Power BI would cause unwanted behavior Fixed an issue when zooming to a single feature (point) on the map would zoom in too closely Removing location data from the XY or location field-wells now resets the component and mirrors all other Power BI visuals on the report page Fixed an issue where inputting the wrong ArcGIS Enterprise URL would not display an error message Fixed an instance of features losing their symbology after making a selection or slicing data Fixed an issue when updating an underlying dataset would not refresh the Time slider Fixed an issue with certain layers created in ArcGIS Enterprise not responding to selections made in a Join layer Fixed an issue with features on the map not filtering in a Join layer Fixed a rare instance where signing into the component from a blocking page would not work Fixed an issue where the lock extent feature was ignored when adding certain reference layers to the map Fixed a rare issue when latitude and longitude values would not populate on the map Fixed an issue with honoring filters made in a layer from ArcGIS Online Fixed an issue when making selections in a feature layer (with points) under the Drive time widget would not update properly Fixed an issue where multiple toast messages would appear on the map when making selections in Drive time Fixed multiple issues related to 'Lock extent' and honoring the settings Fixed and cleaned up an issue in Power BI Report Server when clicking on the 'Help' button Design polishes: Added a missing tooltip when navigating through the breadcrumb trail under the Reference layer widget Updated the watermark text when connecting to an ArcGIS Enterprise URL Updated text for the Drive time widget Updated text when selecting a point-based layer in Drive time Quality of life updates: Added a message when attempting to use the Selection tools on a hidden layer Added a message and disabled Selection tools when attempting to interact with layers that cannot be selected or have selections made on them Added documentation to cover PKI and IWA support Added documentation to cover Drill-through support in Power BI Pressing 'Enter' on your keyboard after typing an ArcGIS Enterprise URL will open the sign in dialog Refined caching to improve performance on the map Refactored and updated core components to improve performance (related to Power BI Desktop's infrastructure updates) Selecting 'Use current location' in the search widget now works in Power BI Desktop Removed and cleaned up a number of toast messages when using Drive time ---- As mentioned in my last post, the goal of these fixes and UI/UX polishes is to make it easier to navigate and create meaningful maps for your report. As we continue to move toward the unified experience across all ArcGIS for Microsoft 365 visuals, 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

ArcGIS for Power Automate is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2022.1.6 update is a quality release. Performance improvements and bug fixes have been made for the following features.  This release will start deploying between August 29th, 2022, and August 30th, 2022. It may take up to 48 hours to push out to all regions (up to two weeks for government-level sites).  If you do not see the changes, you may need to clear your cache and restart your web browser to see the changes in Power Automate. As always, please let us know of any improvements or issues you want to chat about. --- Credit consumption A bug was identified in the ArcGIS for Power Automate connector when using the geoenrichment action. Originally, when a flow was created using this action, there was a miscalculation for the amount of credits needed to complete the action. As an example, the following flow is using an address column from a SharePoint list. In this list, there are five addresses. I created a 30-minute drive time buffer around each of those addresses and picked a variable to investigate.    Prior to this release, there were instances where the geoenrichment process miscalculated the results and thus overcharged the credits to the ArcGIS Online organization.  Credit consumption in v2022.1.5.   Credit consumption in v2022.1.6. We will keep a close eye on credit consumption for all of the other actions in our connector and make any necessary fixes if we see something out of the ordinary.    Creating a feature layer from a SharePoint list In ArcGIS for Power Automate, you can create a feature layer from a wide range of sources. One of the most common sources for data in the Microsoft ecosystem is SharePoint. Recently, there was a change in SharePoint that changed the names of columns under the hood of a SharePoint list. These changes seem to apply to lists that were created from an Excel table.  For example, below is a list that I created from an Excel file. I have a name for each of my columns; Address, Variable.  However, when I dig into the list settings, I see that the fields are named something completely different; Title, field_2. I can see this at the end of the URL.  Field=Title Field=field_2 This was causing some unwanted behavior in our connector when attempting to search for a column named "Variable". This was quite noticeable when attempting to create a feature layer from a SharePoint list. We have now fixed this issue. You can now use the names of the fields from a SharePoint list and the flow will succeed.  Creating a feature layer using this method in v2022.1.5. Creating a feature layer using this method in v2022.1.6. ---- As we continue to move toward the unified experience across all ArcGIS for Microsoft 365 visuals, 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

ArcGIS for Power Automate is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2022.1.5 update is a quality release. Performance improvements and bug fixes have been made for the following features.  This release will start deploying between August 11th, 2022, and August 12th, 2022. It may take up to 48 hours to push out to all regions (up to two weeks for government-level sites).  If you do not see the changes, you may need to clear your cache and restart your web browser to see the changes in Power Automate. As always, please let us know of any improvements or issues you want to chat about.   ----   Geocoding (not stored) A bug was identified in the ArcGIS for Power Automate connector when using an API key and geocoding locations in a flow. If the option "no" was chosen under "Store Results", the lookup process would fail and then the flow would ultimately fail.    This issue has been resolved and you can now choose any option and receive the appropriate results. This is an important fix because you might have your API key configured to not store results when geocoding.    Webhook creation when updating a connection In Power Automate, you are required to keep your connections and credentials updated on a consistent basis. ArcGIS for Power Automate follows the same rules and connections to ArcGIS Online must be refreshed every so often. In rare cases, if a flow contained a trigger to an ArcGIS feature service, the update of those credentials would create an additional webhook on the feature service itself. This ultimately caused an issue on the feature service as there is an upper-limit of 5 webhooks that can be created. This issue has now been resolved. When a flow has its connection updated, the associated trigger and webhooks are updated and additional items are not created. This helps mitigate the new webhook creation on a feature service and does not max out the number of webhooks allowed.  Bug fixes and polishes galore! In this release, we have squashed a ton of bugs and made some performance improvements to the connector.  ---- As we continue to move toward the unified experience across all ArcGIS for Microsoft 365 visuals, 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