nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Joins using text fields are broken

JCable

We have discovered that a side effect of yesterday's 2024.2.550 update has resulted in text-based joins to no longer work. Files that had existing text-joins (setup using the previous version) are now broken and new joins fail to find any matches during validation. This is a major bug that has needs to be fixed immediately!

Find more posts tagged with

Mapping

Power BI Desktop

Accepted answers

NaZhang_Esri

Hi @JCable and @LydiaStekkinger ,

Thank you for bringing this to our attention. We are pleased to inform you that the bug you reported has been resolved in the latest update of ArcGIS for Power BI (version 2024.2.560). To access the fix, please restart Power BI.

Should you encounter any further issues or have additional questions, please don't hesitate to reach out. We're here to help!

cc: @AlagiriVenkatachal

All comments

JCable

ArcGIS Enterprise version: 10.9.1

Power BI version: 2.138.1004.0

ArcGIS for Power BI version: 2024.2.550

AlagiriVenkatachal

Hi @JCable,

Could you please provide more context or details on the issue you are seeing? When you say text-based joins, are these joins made between one or more fields that are of data type: "string" between Power BI and ArcGIS Feature service layer?

Could you please provide more details or steps to reproduce this issue?

Thanks,

Alagiri

JCable

Yes, I am trying to create a join between a table in Power BI and an ArcGIS Feature Service layer. When I set the 'Power BI data' and 'Feature layer' field dropdowns to matching string fields, I get an error that says "No match. Field selection did not yield any results." and I cannot create the join. This worked as recent as last week

The error does not occur if I select numerical fields.

NaZhang_Esri

Hi @JCable,

Thanks for letting us know! The text based join works fine on my side. Much appreciated if you could provide the detailed steps for us to reproduce like @AlagiriVenkatachal mentioned.

AlagiriVenkatachal

Hi @JCable

If the data can be shared with us, could you please share the sample .pbix file and the feature layer so we can look into this? From my internal tests, I was able to join two fields that are data type: 'string'/'text' between Power BI dataset and ArcGIS Feature layer

JCable

Are you using a layer from ArcGIS Online? I just tested with a layer from AGOL and I was able to create a join.

But my organization uses ArcGIS Enterprise and that is where I am seeing the error. Can you test with ArcGIS Enterprise?

NaZhang_Esri

Hi @JCable and @LydiaStekkinger ,

Should you encounter any further issues or have additional questions, please don't hesitate to reach out. We're here to help!

cc: @AlagiriVenkatachal

LydiaStekkinger

Thank you for solving this!

TravisLoseke1

We are not able to get the joins to work with ArcGIS Enterprise. We are consistently getting an error when trying to select on the map after the join is made.

GIS-celVlaams-Brabant

Hi @NaZhang_Esri

We are also running into issues with the join layer. I’m currently on version 2024.2.500.0 and I can't seem to upgrade to a more recent version (not by installing the latest Power BI version manually from Microsoft.com or by downloading it through the Microsoft Store).

I have setup a join-layer and a filter to zoom in on different custom polygons. The issues I have are as follows:

The join layer does work for a bit.. but stops working once I try to use the select tool.
The select tool does not work at all.
When join layer is "working", the map sometimes does not react to a filter and the filter needs to be clicked once more to have an effect.
When going from one filter to another, often there is smooth transition, but other times it just jumps.

We are just starting to explore the option of working with Power BI (and the ArcGIS integration). However, the initial impression left us sligthly dissapointed. Fingers crossed this can be resolved.

Best regards,
Wouter

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.