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

Question

&nbsp;Firstly, the Update File Properties&nbsp; in the action sequence has been working pefectly&nbsp; until we introduced mandatory checkouts in the&nbsp; sharePont document library.&nbsp;Delay (10s) and Get file properties I added to day for debugging purposes.&nbsp;&nbsp;No the strange thing is I manully check in the document and trigger the Logic App.&nbsp;The logic app successfully checks out the document. Here is the output&nbsp;&nbsp;&nbsp;headers": {
        "X-SharePointHealthScore": "2",
        "X-MS-SPConnector": "1",
        "X-SP-SERVERSTATE": "ReadOnly=0",
        "DATASERVICEVERSION": "3.0",&nbsp;&nbsp;&nbsp;However, the Update fails with this odd error:&nbsp;&nbsp;&nbsp;&nbsp; "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.....&nbsp;&nbsp;&nbsp;It is complaining that I have checked out file; which I had to do in the previous acton!!!!!!&nbsp; The document is not open in any browser tab or desktop. Also, I have set up the all the connections under the same account.&nbsp;Update:&nbsp;&nbsp;I wonder if Power Automate is any better&nbsp;?

daniel westerdale · Accepted Answer

Hmmmmmmm,&nbsp; the answer is obvious ( just not to me ).&nbsp;Both Update Item and Check out actions need to reference the same connection&nbsp; in order facilite and orderly deployment between enviroments ( and not to appear as two different users) . You can make the required changes in&nbsp; UI or in the code view ( see below(.&nbsp;&nbsp; "type": "ApiConnection",
                    "inputs": {
                      "host": {
                        "connection": {
                          "name": "@parameters('$connections')['sharepointonline']['connectionId']"
                        }
                      },&nbsp;&nbsp;&nbsp;

Forum Discussion

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

1 Reply

Resources