Getting file properties for current item within "apply to each"

[David2831]

I am trying to build a flow to delete all files in a SharePoint library older than a few days.

This seemed simple, but I am having trouble with a get file properties inside the "apply to each" loop.  I want to check the created date for the current file and test, and do this over and over for each file.

Here is my flow =

When trying to save, I get an error =

Flow save failed with code 'OpenApiOperationParameterValidationFailed' and message 'Input parameter 'id' validation failed in workflow operation 'Current_file_properties': The parameter with value '"@items('Apply_to_each_2')"' in path 'id' with type/format 'Object' is not convertible to type/format 'Integer/int64'.'.

What am I doing wrong?

And also, am I on the right track with the condition control and my test of "created date" is less than "past time"?  Or will these not compare the way I think they will?

[ekarim2020]

Try using the ID for the Current file properties action:

Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

[David2831]

OK, if that would work, then that means calls to "Get Files(Prop only)" from inside the "Apply to each" loop will return only info about the current object the loop is working on.  So then do I need a second get file properties to get the current items ID and created date?  Or can I just keep referencing the "Get Files(Prop only)" for that info?

[ekarim2020 · Accepted solution]

From what you have said, Yes, the Get files (properties action) should provide what you need. In that case the flow would be simpler.  We would loop through each item (file) returned by Get files (properties action) and reference the Created and ID fields:

Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

[ekarim2020]

Next you could add a filter to your Get files (properties action) action, and then not need to use the condition action:

The flow would look something like this now - as the Filter query will have selected the records meeting the criteria for deletion. The flow would run much quicker too.

Ellis
____________________________________
If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

[David2831]

That worked, my flow works now.  Ran with a few test files and the older ones were deleted, new ones remained.

For anyone that's interested in the future, the logic of my condition control and my test of "created date" is less than "past time" does seem to work for this.

But, you cannot target a file for deletion with the "ID" field, you have to use "Identifier" instead 🙂

Thank you.

[David2831]

Wow, just now noticed this addition, that looks amazing.   I will try that.

Thank you!

[David2831]

Question, I am not familiar with the "Compose action".  What is it doing for me in your revised example?

[David2831]

Tried making this myself based on your filter idea, sadly it gives an error that that filter syntax may be off.

I am reading more about ODATA language now, didn't know about this and it looks useful.

The expression "Created It '2021-11-18T15:55:33.5737082Z'" is not valid. Creating query failed.

clientRequestId: bd4713c4-70d9-4b4a-8d2a-3f5d866b0517
serviceRequestId: bd4713c4-70d9-4b4a-8d2a-3f5d866b0517

[ekarim2020]

Please check that:

(1) The Past time is enclosed in single quotes:

AND

(2) that the operator is lt (LT for less than) and not lt (IT).

You should be able to copy-and-paste the expression below into the Filter Query if needed:

 Created lt '@{body('Get_past_time')}'

If you still get the error:

(1) Please show me a screenshot of the Get Files action

(2) And please send the expanded screen of the Get files action. Note the Filter Query.

Ellis

[David2831]

You got it with your second point above, I was using 'it' with a uppercase I.  Everything works now.

Thank you for the information, I will learn more about ODATA language.