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 / Sharepoint list owshid...
Power Automate
Unanswered

Sharepoint list owshiddenversion property (Json)

(0) ShareShare
ReportReport
Posted on by

Hello,

I am buiding a flow where I use the version history of a sharepoint list following the process described on the link (http://johnliu.net/blog/2018/5/microsoft-flow-sharepoint-trigger-on-specific-fields-changed-via-sp-http-request?rq=trigger%20flow).

 

In this tutorial they use the "VersionLabel" property, buy looking into the Json of versions I realize that there is another property that may be more interesting (is a number, not a string), this property is "owshiddenversion".

 

I see that in some point of the historical versions of the list I am working with, the number of owshiddenversion is higher than VersionLabel.

Do you think I could use owshiddenversion?

What is the difference between both?

 

Regards!

 

Categories:
I have the same question (0)
  • aprildunnam Profile Picture
    704 on at

    The way I understand the owshiddenversion is it isn't tied to versioning.  It's a special property that SharePoint uses to aid in conflict detection.  It's how SharePoint tells if you are trying to update an old version of a form.  For example, say you and I are in the edit screen for the same record in SharePoint at the same time.  If you save your change before me  then i go in to save my change, the owshiddenversion property is going to kick in and throw an error because I'm in an older version of the form.  When I loaded the form it was owshiddenversion 0 but after you saved it then it became version 1.  When I got to save mine it does a check for the most recent version and if they don't match is detects a conflict.  So to answer your question, no i don't think you should use that property instead because the use case is different.

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
Haque Profile Picture

Haque 589

#2
Valantis Profile Picture

Valantis 459

#3
11manish Profile Picture

11manish 382

Last 30 days Overall leaderboard