As the subject says - update file properties only shows "File size" from previous file actions when trying to select the ID.
tried getting file metadata from path, getting file properties - all just resturn the File Size property when I click into the ID field....I need the ID...?
Here I'm focused on the ID input field;
If I click into another field, (other than ID, like Title), then all the dynamic properties pop up!
So am I using this incorrectly?
Kind regards,
R
Solved! Go to Solution.
OR you can do this, which I just figured out on a hunch, because a document library is basically a list;
Tested, works, done.
Kind regards,
R
Hi @Anonymous,
Which property that you would like to update with, the file itself, or the added column fields in the Library item?
For the file itself, please switch to update file Action,
If you would like to update the file properties added as additional column in the Library item, we need to do it in the following way:
Image reference:
More details about the usage of “Update file properties” action and “Update file” action, read the article as below:
Usage of “Update file properties” action
Regards,
Michael
Just guessing... maybe the Id received as opuput of "Create File" is a string; but ID expected as input by "Update File properties" needs to be an Integer.
If so, int conversion function defined in WDL can help you
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language
Hope it helps
Proud to be a Flownaut!
I understand this mechanism but it is a shame how complicated this is. Flow is created for the non developers to create magic quickly, now we force them to make a simple 'four line' for loop in a *very* complicared way: three pages of printscreen required to document it.
- does not even documents it properly as this dynamic label items dont show from which action they were selected: for example ID item gives different output from different action of the sharepoint connector - obscured.
* why these actions dont take both integer and path and also identifier string as input?
* little labels should show detailed syntaxat least on mouse hoover-on
g.
I agree it is a bit frustratring to realize something that should be implemented in two-three simple steps needs workarounds.
Let's hope Flow team will continue working hard to improve this tool as they have been doing in the last months. I am working mainly with Sharepoint based Flows, and the improvement on this area has been really huge, although there is still a lot of work to be done.
Proud to be a Flownaut!
That was my solution at the end. After creation / copy you research the whole library with
(found somewhere here in the community) in the Get files Filter query
then you need to hijack the ID from the one element list using a variable
Thanks for sharing!
Proud to be a Flownaut!
OR you can do this, which I just figured out on a hunch, because a document library is basically a list;
Tested, works, done.
Kind regards,
R
It is odd to me that you are able to use the ItemID dynamic content in Update Item; however, I tested it and could not.
It might be specific to my method, not sure if relevant but....;
Still working for me - I've also discovered that this trick works inside PowerApps as well, meaning I can directly update file properties using an edit form that has the library as a data source.
With this, I can just update custom columns on a library direct from PowerApps without updating the actual file, which is a massive win for some of our "doc management and approval flow" apps.
Kind regards,
R
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
User | Count |
---|---|
40 | |
36 | |
36 | |
34 | |
27 |
User | Count |
---|---|
39 | |
38 | |
34 | |
31 | |
25 |