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

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