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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
Max_701
Helper I
Helper I

Dataflow Gen1 - Index Issue

I have a Gen1 Dataflow which gets fed into a linked entity in a child dataflow. The whole setup looks like this 
REST API ->Parent DF1 ->Child DF2 ->Report. Parent DF1 has an index column which goes like this 1,2,3.... but when I import it in child DF2, this gets renumbered to 140,141,142....

Has anybody else also faced this issue & is there a work around to make sure that the index values are amintained over this setup.

Thanks in Advance!

1 ACCEPTED SOLUTION
collinq
Super User
Super User

HI @Max_701 ,

This is actually by design I believe.  This is because each "table" is getting its own index.  So, the parent gets one and then the child gets another one.  There are a few workarounds depending on how you want to do it.  But, the easiest is probably to generate the index after the loading of the child table.

Another option would be to change the linking - so that the child is not referenced but rather linked (but that might not be really the way you want to do it).




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

Proud to be a Datanaut!
Private message me for consulting or training needs.




View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Hi @Max_701,

 

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.

 

Regards,
Vinay Pabbu

Max_701
Helper I
Helper I

Thanks for the response! You mentioned another way would be to chnage the linking - could you please elaborate? Currently the DF2 uses only linked entitites from multiple parent dataflows, if this helps in better understanding of the setup.

Anonymous
Not applicable

Hi @Max_701,

 

when you use linked entities, Power BI runs the steps again — so the index gets recalculated and doesn't stay the same. To keep the original index from the parent dataflow, you need to use a computed entity, which actually brings in the data as it is, without redoing the steps.

 

Regards,

Vinay Pabbu

collinq
Super User
Super User

HI @Max_701 ,

This is actually by design I believe.  This is because each "table" is getting its own index.  So, the parent gets one and then the child gets another one.  There are a few workarounds depending on how you want to do it.  But, the easiest is probably to generate the index after the loading of the child table.

Another option would be to change the linking - so that the child is not referenced but rather linked (but that might not be really the way you want to do it).




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

Proud to be a Datanaut!
Private message me for consulting or training needs.




Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors