Why don't I see the join layer option in ArcGIS for PowerBI?

570
2
Jump to solution
06-30-2022 07:06 AM
RodPBI
by
New Contributor III

I have met the following pre-requisits for joining my AGOL layer:

  1. I created the ArcGIS for PowerBI visual and logged into my ArcGIS account
  2. My non-spatial data contains a field that matches to my spatial data
  3. I loaded the spatial layer (a line layer) from my AGOL account
  4. I placed my join field from my non-spatial data into the join field well

Also, my User Type is Creator...

According to these instructions I should simply see the join option when I select layers options in the layer list,

Join layers—ArcGIS for Power BI | Documentation

but alas, no join layer option! (I blurred the layer name to preserve privacy)

RodPBI_1-1656597811996.png

 

 

 

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
AnthonyLatini
Esri Contributor

Hey there @RodPBI ! It sounds like Power BI just needed some coffee! 

I believe that might be the case with this issue. Power BI in general has upper limits on memory consumption and processing power. It might have just taken a bit to process through that since 1.7 million records (and even the 400k is pushing it somewhat) is quite a bit. 

 

Please let me know if you see any other issues with this! 

View solution in original post

0 Kudos
2 Replies
RodPBI
by
New Contributor III

Several minutes after posting this question, I went back to the ArcGIS visual and tried again, and this time the option was there. 

RodPBI_0-1656599341853.png

I had not changed anything (all I did was get a cup of coffee).  All I can imagine is that there must be quite a delay due to the amount of data I have... My non-spatial data contains 1.7M records... but filtered on the page to about 400K.  The Spatial data contains about 4600 records....

0 Kudos
AnthonyLatini
Esri Contributor

Hey there @RodPBI ! It sounds like Power BI just needed some coffee! 

I believe that might be the case with this issue. Power BI in general has upper limits on memory consumption and processing power. It might have just taken a bit to process through that since 1.7 million records (and even the 400k is pushing it somewhat) is quite a bit. 

 

Please let me know if you see any other issues with this! 

0 Kudos