Forum Discussion

Acrix's avatar
Acrix
Regular Visitor
4 months ago
Solved

After transformed data, inside Table View the col go to the end

How if after I split cols in query editor and remove the 2nd col, then close and apply. In Table View the col go to the end, in editor it looks normal, how to fix

  • What you’re seeing isn’t a bug—it’s how Microsoft Fabric / Power Query behaves after applying transformations.

    Why this happens

    In Power Query Editor, the column order reflects the step-by-step transformations you applied.

    But once you Close & Apply, the model (Table View) may:

    • Reorder columns based on internal schema updates
    • Treat newly created columns (like from Split Column) as “added later”, so they appear at the end
    • Ignore visual order unless it’s explicitly enforced in the query steps

    How to fix it (best practices)

    ✔️ 1. Explicitly reorder columns in Power Query

    After your transformations:

    • Go to Home → Choose Columns → Reorder Columns
    • Or drag columns manually into the correct order

    👉 This creates a step like: Reordered Columns

    This step locks the order when loaded into Fabric.


    ✔️ 2. Check the last applied step

    Sometimes the issue happens because:

    • You reordered columns before splitting/removing columns

    📌 Fix:

    • Move the Reorder Columns step to the very last step in Applied Steps

    ✔️ 3. Use “Choose Columns” instead of removing

    Instead of:

    • Split → Remove column

    Try:

    • Split → Choose Columns (keep only what you need)

    This avoids hidden reordering issues.


    ✔️ 4. Verify in Data Model vs Query

    Remember:

    • Query Editor = transformation logic
    • Table View = final model structure

    So always ensure the final step defines the structure


    Pro tip (advanced)

    If you’re comfortable with M code:

    • Add this at the final step:
    Table.ReorderColumns(Source, {"Col1", "Col2", "Col3"})

    This guarantees exact ordering regardless of earlier steps.


    Bottom line

    Your column moved because Fabric treats it as a new column added late in the pipeline.
    👉 The fix is simple: force column order as the last step

12 Replies

  • Hi Acrix,

     

    I hope you selected columns in the last step, if it's not working then there's no other solution to reorder columns in table view

  • Hi Acrix

     

    Inside the table view the columns will go to the end, however when you build a report you can arrange the columns in your visuals however you want. 

    ENd users don't see the table view, only the report developer does.  

  • What you’re seeing isn’t a bug—it’s how Microsoft Fabric / Power Query behaves after applying transformations.

    Why this happens

    In Power Query Editor, the column order reflects the step-by-step transformations you applied.

    But once you Close & Apply, the model (Table View) may:

    • Reorder columns based on internal schema updates
    • Treat newly created columns (like from Split Column) as “added later”, so they appear at the end
    • Ignore visual order unless it’s explicitly enforced in the query steps

    How to fix it (best practices)

    ✔️ 1. Explicitly reorder columns in Power Query

    After your transformations:

    • Go to Home → Choose Columns → Reorder Columns
    • Or drag columns manually into the correct order

    👉 This creates a step like: Reordered Columns

    This step locks the order when loaded into Fabric.


    ✔️ 2. Check the last applied step

    Sometimes the issue happens because:

    • You reordered columns before splitting/removing columns

    📌 Fix:

    • Move the Reorder Columns step to the very last step in Applied Steps

    ✔️ 3. Use “Choose Columns” instead of removing

    Instead of:

    • Split → Remove column

    Try:

    • Split → Choose Columns (keep only what you need)

    This avoids hidden reordering issues.


    ✔️ 4. Verify in Data Model vs Query

    Remember:

    • Query Editor = transformation logic
    • Table View = final model structure

    So always ensure the final step defines the structure


    Pro tip (advanced)

    If you’re comfortable with M code:

    • Add this at the final step:
    Table.ReorderColumns(Source, {"Col1", "Col2", "Col3"})

    This guarantees exact ordering regardless of earlier steps.


    Bottom line

    Your column moved because Fabric treats it as a new column added late in the pipeline.
    👉 The fix is simple: force column order as the last step

  • Hi Acrix,

     

    Try below fixes:-

     

    Explicitly reorder columns in Power Query (Best Practice) - After splitting the columns add another step go to transform -> Reorder columns and order the columns in correct order.

     

    🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
    💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
    🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
    🔗 Curious to explore more? [Discover here].
    Let’s keep building smarter solutions together!

    • Acrix's avatar
      Acrix
      Regular Visitor

      Yes, I did make the Reordered Column, last step, it looks good in Editor after transformed it still go to the end, I can't even move it back by dragging in Table View

      • grazitti_sapna's avatar
        grazitti_sapna
        Icon for Super User rankSuper User

        HI Acrix,

         

        Try select coulmns instead of remove columns : go to Choose Columns then Select Columns and select the columns in the order in which you want to show them, this should fix your issue.

  • v-dineshya's avatar
    v-dineshya
    Icon for Community Support rankCommunity Support

    Hi Acrix ,

    Thank you for reaching out to the Microsoft Community Forum.

     

    Hi grazitti_sapna  and tayloramy Thank you for your prompt responses.

     

    Hi Acrix , could you please try the proposed solutions shared by grazitti_sapna  and tayloramy  ? Let us know if you’re still facing the same issue we’ll be happy to assist you further.

     

    Regards,

    Dinesh

    • Acrix's avatar
      Acrix
      Regular Visitor

      Its ok I just ignored the Table View, ty

  • You can also try:

     

    Untick 'Enable Load' in Power Query for the relevant query

    Apply changes

    Go back to Powerquery

    Tick 'Enable Load' in Power Query for the relevant query

    Apply changes

     

    That should then reload the entire query to Table View as if it was a new query being added.

    In table view, you can also remove the DAX that refers to the query, replace it with something else as a holder and then put the original DAX back in. That should refresh it, but calculated columns will also move to the beginning. These can however be re-ordered if needed by deleting and re-creating in the positions you want.

     

    These are just things you could experiment with. Re-ordering calculated columns is a bit of a pain though..

  • v-dineshya's avatar
    v-dineshya
    Icon for Community Support rankCommunity Support

    Hi Acrix ,

    Thank you for reaching out to the Microsoft Community Forum.

     

    Hi Mohamed32  and pbix1  Thank you for your prompt responses.

     

    Hi @Acrix , could you please try the proposed solutions shared by Mohamed32  and pbix1 ? Let us know if you’re still facing the same issue we’ll be happy to assist you further.

     

    Regards,

    Dinesh

    • v-dineshya's avatar
      v-dineshya
      Icon for Community Support rankCommunity Support

      Hi Acrix ,

      We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

       

      Regards,

      Dinesh