SOLVED

Logic App Update File Properties throws an exception after a SPO file successful checkout

Iron Contributor

 

Firstly, the Update File Properties  in the action sequence has been working pefectly  until we introduced mandatory checkouts in the  sharePont document library.

 

Delay (10s) and Get file properties I added to day for debugging purposes.

 

check out failure.png

 

No the strange thing is I manully check in the document and trigger the Logic App. 

The logic app successfully checks out the document. Here is the output

 

 

 

headers": {
        "X-SharePointHealthScore": "2",
        "X-MS-SPConnector": "1",
        "X-SP-SERVERSTATE": "ReadOnly=0",
        "DATASERVICEVERSION": "3.0",

 

 

 

However, the Update fails with this odd error: 

 

 

 

 "body": {
        "status": 400,
        "message": "The file \"https://mydev.sharepoint.com/sites/DansDoodles/test.dscs\" is checked out for editing by i:0#.f|membership|Daniel.....

 

 

 

It is complaining that I have checked out file; which I had to do in the previous acton!!!!!!  The document is not open in any browser tab or desktop. Also, I have set up the all the connections under the same account.

 

Update:  

check out failure and more weirdness.png

I wonder if Power Automate is any better :unamused:?

1 Reply
best response confirmed by Daniel Westerdale (Iron Contributor)
Solution

Hmmmmmmm,  the answer is obvious ( just not to me :facepalm:).

 

Both Update Item and Check out actions need to reference the same connection  in order facilite and orderly deployment between enviroments ( and not to appear as two different users) . You can make the required changes in  UI or in the code view ( see below(.

 

 

 "type": "ApiConnection",
                    "inputs": {
                      "host": {
                        "connection": {
                          "name": "@parameters('$connections')['sharepointonline']['connectionId']"
                        }
                      },

 

 

 

1 best response

Accepted Solutions
best response confirmed by Daniel Westerdale (Iron Contributor)
Solution

Hmmmmmmm,  the answer is obvious ( just not to me :facepalm:).

 

Both Update Item and Check out actions need to reference the same connection  in order facilite and orderly deployment between enviroments ( and not to appear as two different users) . You can make the required changes in  UI or in the code view ( see below(.

 

 

 "type": "ApiConnection",
                    "inputs": {
                      "host": {
                        "connection": {
                          "name": "@parameters('$connections')['sharepointonline']['connectionId']"
                        }
                      },

 

 

 

View solution in original post