Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
tctrout
Resolver III
Resolver III

Online Refresh Fails due to adding Index Column

Hello Community,

I have an online refresh failure where we were able to identify the root cause and fix it.  However, I believe it to be a bug and wanted to know if anyone else has experienced this.  

 

Background:

We have Premium Capacity and leverage a data gateway. 

 

The Issue:

We leverage the technique of creating surrogate keys for all of our dimensions and then use merge statements to 'join' the dimensions back to the fact table where we then only display the surrogate key created.  We have been using this technique for almost a year and have never experienced an issue until now.

 

The surrogate key created on the dimesnion tables is nothing more than the Index Column and we completely use the GUI to do the build.  

 

The solution refreshes fine locally, no issues.

 

However, when we publish it online, we get errors and it doesnt refresh.  Reading thru the cryptic error messages we determined that the error is ocurring on Index Column creation.  The gist of the error is that it refers to the Index Column step indicating that a function was pass 5 parameters when it was expecting 2. 

 

 Reading thru the Mcode we realize that PowerBI is now inserting an additional step when creating the Index Column, it is changing the data type to Int64.Type.  This change is causing the issue, in bold below.

 

= Table.AddIndexColumn(#"Trimmed Text", "Index", 1, 1, Int64.Type)

 

We are not sure when Microsoft introduced this change, but we are certain that it was a recent change because since we have leveraged this technique for a year we can go back to prior builds and see that using the GUI Index Column use to only produce this Mcode
= Table.AddIndexColumn(#"Trimmed Text", "Index", 1, 1)

 

The Fix:

We modified the existing PBIX file, removing the Int64.Type reference from the Mcode, and the soltuion now refreshes online with no issue.

 

The Question:

Has anyone else experienced this or possibly explain what has changed and why this is occuring?  We will be creating a ticket with Microsoft as we do not believe that using the GUI to create an Index should cause any errors when refreshing online.  

1 REPLY 1
GilbertQ
Super User
Super User

There are potentially changes that happen in PQ from time to time.

I would suggest as you said log a call to MS to get to the root cause.




Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Kudoed Authors