web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Using dynamic values f...
Power Automate
Unanswered

Using dynamic values for Site Address and List Name in SharePoint Create and Update Actions

(0) ShareShare
ReportReport
Posted on by 157
Not technically a question, so lemme know if I'm supposed to share elsewhere.
 
I do a lot of stuff with SharePoint Items based on config data. I imagined an Issue with Update item as it hard binds to Column normally.

However, when the Site Address and List Name are dynamic, it exposes an Item property (named that for no obvious reason) in which you can specify an object with Column/value pairs. I created a series of wrapped flows that would do the create/update via the SharePoint HTTP Request Action. The object of Column/value pairs was exactly what I wanted because I can build the object at runtime.

Anyway, I would have saved myself time had I known this, so I hope others benefit. Always one to find that silver lining. I learned a lot about doing stuff with SharePoint with HTTP. I now have a flow that can get Column info, for example. I'll extend it to do other stuff, sparing the caller a lot of the details.
 
GenAI still isn't where it needs to be. I consult multiple chatbots regularly, but none of them caught this; they sucked me into the wrong solution, just faster.
Categories:
I have the same question (0)
  • Sunil Kumar Pashikanti Profile Picture
    2,074 Moderator on at
     
    Nice find. This behavior surprises a lot of people. When the Site Address and List Name are dynamic, Power Automate can’t pre‑load the list schema, so it switches to the generic Item object. That’s why you can pass your own colunm/value pairs at runtime. It’s actually a great pattern for reusable flows or config‑driven scenarios.

    One tip for others using this approach, make sure you use internal column names, and be aware that lookup, people, and taxonomy fields still need their structured values. For anything more advanced (system fields, folders, large lookups), the HTTP action is still the right choice. But for standard create/update operations, the dynamic Item object is a huge time‑saver.

    Great share, this will help a lot of folks building flexible SharePoint flows.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Vish WR Profile Picture

Vish WR 889

#2
Valantis Profile Picture

Valantis 830

#3
Haque Profile Picture

Haque 505

Last 30 days Overall leaderboard