When new Version is created

[jitendrasingh]

I want a flow which will run only when any new version of document is created in One drive for business. Can anyone help in creating this flow

[Expiscornovus]

Hi @jitendrasingh,

As far as I am aware every modification to a file in OneDrive for Business will result in a new major version of the file.

So, it should be sufficient to use the When a file is modified (properties only) trigger action in your flow:

https://docs.microsoft.com/en-us/connectors/onedriveforbusiness/#when-a-file-is-modified-(properties...

Hope this helps a bit?

[jitendrasingh]

Hi @Expiscornovus 

 the flow you mentioned  triggers action on when file is created as well as when file is modified (New Version). I need a flow which will trigger only when file is modified and not when file is created.

[Expiscornovus]

Hi @jitendrasingh,

Are you sure? Isn't it just the 2.0 version of the newly created file (which is a modification?) As far as I am aware that action only triggers when a file is modified.

For the create event Microsoft has a different trigger action called:

https://docs.microsoft.com/en-us/connectors/onedriveforbusiness/#when-a-file-is-created-(properties-...

[jitendrasingh]

Hi @Expiscornovus 

Yes I am sure.. I tested many times... It not only triggers for modification (version 2.0 or later) of file but also for creation of file .. You can test the same 

[Expiscornovus]

Hi @jitendrasingh,

I also tried reproducing this and I am unable to. For me it only triggers when modifying the file, starting from the 2.0 version of a file.

Can you share some screenshots of your setup and your flow history. Let me see if I can reproduce it with your setup.

[jitendrasingh]

Hi @Expiscornovus 

I create similar flow but again it triggered when i created a file in it. Please find below snapshots of same

[Expiscornovus]

Hi @jitendrasingh,

Thanks for sharing your setup. Looks pretty similar to mine. 

Another validation question. How are you testing? Are you uploading a file or are you creating it via the new button?

And if you are using the second testing scenario are you renaming the file?

I was doing the same thing in my tests and also triggered the flow. Because the renaming action will create a second version of the file, which makes it seem like it is triggering for a newly created file.

[jitendrasingh]

Hi @Expiscornovus 

I am uploading the file with same name & it is updated as new version.

The flow triggers when new file is uploaded as well as when new version of same file is uploaded.

I want flow to run only when new version is uploaded (Version 2.0 onwards) and not on Version 1.0 

[Expiscornovus]

Hi @jitendrasingh,

Thanks for sharing. With an upload I am also able to reproduce this behaviour.

I think we can use the Etag and use the second part of that to retrieve at the version. We can use a greaterorequals to make sure it is at least 2.0.

Can you add the following expression as a trigger condition to your action?

@greaterOrEquals(replace(split(triggerOutputs()?['body/ETag'], ',')[1], '"', ''), '2')

[jitendrasingh]

Hi @Expiscornovus 

Thanks... I am new to Power automate,Can you share screenshot of the solution you suggested so that i can reproduce same in my environment

[jitendrasingh]

Hi @Expiscornovus 

I have added above expression in my trigger however it is showing flow error .Screenshot attached

[Expiscornovus]

Hi @jitendrasingh,

I noticed in your last screenshot that you are using a different trigger action compared to my example. I was using the When a file is modified (properties only) one in my example.

The trigger outputs of the When a file is modified action you are using is slightly different. 

If you want to keep using the modified action you need to use a different field from the trigger action in the expression, the field entity tag.

In that case the expression would be:

@greaterOrEquals(replace(split(triggerOutputs()?['headers/x-ms-file-etag'], ',')[1], '"', ''), '3')

The trigger condition can be added via the settings of my When a file is modified action. Below is a screenshot of that.

[jitendrasingh]

Hi @Expiscornovus 

I have used the trigger as suggested above however while saving the flow it is showing an error as Invalid Template with the following error

" The template language function 'split' expects its first parameter to be of type string."

[jitendrasingh]

Hi @Expiscornovus 

I have used the trigger as suggested above however while saving the flow it is showing an error as Invalid Template with the following error

" The template language function 'split' expects its first parameter to be of type string."Screenshot of same is shared below

Please help

[Expiscornovus]

Hi @jitendrasingh,

In your screenshot I see a flow run and some headers. I am interested to see what's in those trigger outputs headers. Can you click the show raw outputs link and copy/paste or screenshot that?

Below is an example of the headers I would be expecting for a When a file is modified trigger action.

[jitendrasingh]

Hi @Expiscornovus 

[Expiscornovus]

Hi @jitendrasingh,

I see you are getting an HTTP 202 instead of a HTTP 200. So, it looks like it was still processing the upload when the flow was triggered and this is the reason why it can't find the metadata of your file.

https://blog.encodian.com/2020/03/202-status-code-and-asynchronous-pattern-power-automate/

Out of interest, what kind of files (type and size) are you using in your tests when uploading?

I see your trigger action

[jitendrasingh]

Hi @Expiscornovus 

Actually the flow is showing following error after adding trigger action suggested by you

The details of error on follow up screen is pasted below

As the flow is being saved with errors so there are no triggers with file being uploaded.

[Expiscornovus · Accepted solution]

Hi @jitendrasingh,

It looks like it is the same error as from the previous screenshots. Like we established together the etag field is absent from your trigger outputs. So, it is trying to split on a field which isn't available yet, because the response is a HTTP 202 and not a HTTP 200 with the metadata.

Can you try the expression below. I have slightly adjusted it to handle the scenario where it is empty. Can you test and see if that can handle the HTTP 202 response (which doesn't have an etag yet):

@greaterOrEquals(replace(split(if(empty(triggerOutputs()?['headers/x-ms-file-etag']), '0,0', triggerOutputs()?['headers/x-ms-file-etag']), ',')[1], '"', ''), '3')