Display Order in Item Actions

(1) Share

Report

Posted on by emberkrumwied

142

Searches for my question aren't returning my specific need, so I thought I'd post it here in hopes someone can assist.

In a Power Automate flow, when using an "item" action (create/update), I am curious to know what decides the order in which the fields are displayed. I had thought perhaps it was based on the column order set on the referenced list, but that isn't tracking. Sometimes a newly added list column will appear at the bottom of the action card, other times it will appear somewhere in the middle. It does seem to place any required field at the top of the list, but not in any particular order. Asking to see if there is a way to set that display order (i.e. sort alphabetically).

I am NOT asking about how to set the display order of the result of the action or anything to do with the dynamic or expression content inside a specific field, I am asking about the PA action card itself. See the image below for reference.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Pstork1 69,129 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

From what I've seen it lists all the required fields in the order they were added to the list first, then all the optional fields in the order they were added to the list after. If you use a view to restrict the clients displayed then it uses the order in the view. Required columns still go first and then optional columns. But now it follows the order of the view.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

11manish 849 on at

Like (0)

Report
Copy link

Link copied!

In Power Automate, the field order in “Create item” / “Update item” actions is system-controlled and cannot be customized.

Order is based on internal metadata, not list configuration

Use structured mapping instead of depending on UI layout

Was this reply helpful? Yes No
Suggested answer

Kalathiya 1,690 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @emberkrumwied,

From what I’ve seen, the order of fields in the Power Automate action mostly follows the column order from the SharePoint list view. So if you change the column order in the view it will update in action as well.

Note:

#1. Title column will always remain first even if you change the column order in view.
#2. Required fields will be shown at the top of the action no matter in column order in view.

Please compare view it will be same order as view.

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No
Suggested answer

Haque 1,419 on at

Like (0)

Report
Copy link

Link copied!

Hi @emberkrumwied,

Currently, there is no supported method to explicitly set or control the display order of fields in the create/update item actions in Power Automate. Agreed with @Pstork1, required fields in the order they were added to the list frist, then all the optional fields in the order they were added to the list after. One more is newly added columns may appear near the bottom or somewhere in the middle, depending on how Power Automate internally caches or refreshes the schema.

If you want a more predictable or custom order, a common workaround is to:
Use manual inputs (e.g., Compose or Variables) for your fields in the order you want. Then map those inputs explicitly to the fields in the create/update action. This way, your flow design visually reflects the order you prefer, even if the action card fields themselves do not.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No