Skip to main content
Suggested answer

Strange Power Automate Error with Document Location Records - Could not find a property named 'sharepointdocumentlocationid' on type 'Microsoft.Dynamics.CRM.sharepointsite'.

editSubscribe (0) ShareShare
ReportReport
Posted on by 1,555

I am experiencing some kind of bug with an action card in the Power Automate Flow named “ACEServiceTech - Account | Create SharePoint Folders

In this flow, there is an action card named “Get_Document_Location_of_Parent_Account” and that particular action card uses the following fetch XML query.

  
    
    
    
    
    
    
    
      
    
  

 

When the above fetch XML query is run within XRMToolbox, it returns the expected data as shown below.

XRMToolbox_5F00_XML_5F00_Query_5F00_Document_5F00_Location_5F00_Account_5F00_Results.png

Here is a screen shot of the query as it sits in XRMTool Box.

XRMToolbox_5F00_XML_5F00_Query_5F00_Document_5F00_Location_5F00_Account.png

Here is a screen shot of the Action Card that runs the query.

Action_5F00_Card_5F00_Get_5F00_Document_5F00_Location_5F00_Of_5F00_Parent_5F00_Account.png

 

When the trigger executes, and the Power Automate Flow named “ACEServiceTech - Account | Create SharePoint Folders” runs, the following error occurs.

 

Could not find a property named 'sharepointdocumentlocationid' on type 'Microsoft.Dynamics.CRM.sharepointsite'.

 

Here is a screen shot of the error as it appears.

Action_5F00_Card_5F00_ERROR_5F00_Get_5F00_Document_5F00_Location_5F00_Of_5F00_Parent_5F00_Account.png

The raw outputs are:

{

    "statusCode": 400,

    "headers": {

        "x-ms-service-request-id": "b1e07807-8097-4d82-9d81-60b755b9eb6e,93330c78-7469-40fb-8c01-6ebd041174dc",

        "Cache-Control": "no-cache",

        "Set-Cookie": "ARRAffinity=54e73dbe8141afca6239d255e15e888bc39e320ae8003fe384759a8032d43d15; domain=redacted.crm.dynamics.com; path=/; secure; HttpOnly,ReqClientId=67d17937-7572-402c-90d5-2e71b9d77708; expires=Fri, 22-May-2071 22:39:11 GMT; path=/; secure; HttpOnly; samesite=none,ARRAffinity=54e73dbe8141afca6239d255e15e888bc39e320ae8003fe384759a8032d43d15; domain=redacted.crm.dynamics.com; path=/; secure; HttpOnly",

        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",

        "REQ_ID": "93330c78-7469-40fb-8c01-6ebd041174dc,93330c78-7469-40fb-8c01-6ebd041174dc",

        "AuthActivityId": "091d4c33-ef6d-4589-b8d5-a81226c6d742",

        "x-ms-ratelimit-burst-remaining-xrm-requests": "5970",

        "x-ms-ratelimit-time-remaining-xrm-requests": "1,167.81",

        "OData-Version": "4.0",

        "X-Source": "122272462431724919721011441141332022061874014076891267227202051062441493716183164104,22485162200511001321750103245233212165221094108230521702097896225211838024319417031",

        "Public": "OPTIONS,GET,HEAD,POST",

        "Timing-Allow-Origin": "*",

        "Date": "Sat, 22 May 2021 22:39:12 GMT",

        "Content-Length": "148",

        "Allow": "OPTIONS,GET,HEAD,POST",

        "Content-Type": "application/json; odata.metadata=full",

        "Expires": "-1"

    },

    "body": {

        "error": {

            "code": "0x0",

            "message": "Could not find a property named 'sharepointdocumentlocationid' on type 'Microsoft.Dynamics.CRM.sharepointsite'."

        }

    }

}

 

The raw inputs are:

{

    "host": {

        "connectionReferenceName": "shared_commondataserviceforapps",

        "operationId": "ListRecords"

    },

    "parameters": {

        "entityName": "sharepointsites",

        "fetchXml": "\n  \n    \n    \n    \n    \n    \n    \n      \n    \n  \n",

        "$top": 1

    }

}

This should not be erroring out. I know this because I am running the exact same type of query against a different entity using a different Power Automate Flow and that works without incident.

 

The only difference is that I created that power automate flow on May 6 and I created this one today May 22.

 

I suspect there is a bug that has been introduced between the time I created the flow that works, and the current flow that errors out running the exact same process.

 

The Power Automate flow that works is named “ACEServiceTech - Opportunity | Create SharePoint Folders

 

The action card is named “Get Document Location of Parent Opportunity” and you can see in the screen shot below that it is doing the exact same thing, except it is executing against the opportunity entity as opposed to the account entity.

Action_5F00_Card_5F00_Get_5F00_Document_5F00_Location_5F00_Of_5F00_Parent_5F00_Opportunity.png

You can see that when run today, it executed successfully as shown in the screen shot below.

Action_5F00_Card_5F00_NO_2D00_ERROR_5F00_Get_5F00_Document_5F00_Location_5F00_Of_5F00_Parent_5F00_Opportunity.png

 

The raw outputs are as follows:

 

{

    "statusCode": 200,

    "headers": {

        "Vary": "Accept-Encoding",

        "x-ms-service-request-id": "9b1e71ab-d781-4173-a69b-0a2b505ced14,3360d86e-f8f6-4255-8961-cfcf6a82e552",

        "Cache-Control": "no-cache",

        "Set-Cookie": "ARRAffinity=54e73dbe8141afca6239d255e15e888bc39e320ae8003fe384759a8032d43d15; domain=redacted.crm.dynamics.com; path=/; secure; HttpOnly,ReqClientId=c05f9de9-d928-48f1-8c6d-e9e7a8a4c1f7; expires=Fri, 22-May-2071 22:17:00 GMT; path=/; secure; HttpOnly; samesite=none,ARRAffinity=54e73dbe8141afca6239d255e15e888bc39e320ae8003fe384759a8032d43d15; domain=redacted.crm.dynamics.com; path=/; secure; HttpOnly",

        "Strict-Transport-Security": "max-age=31536000; includeSubDomains",

        "REQ_ID": "3360d86e-f8f6-4255-8961-cfcf6a82e552",

        "AuthActivityId": "54d73ee3-605e-4759-8c18-71b08658125b",

        "x-ms-ratelimit-burst-remaining-xrm-requests": "5986",

        "x-ms-ratelimit-time-remaining-xrm-requests": "1,198.96",

        "OData-Version": "4.0",

        "Preference-Applied": "odata.include-annotations=\"*\"",

        "X-Source": "122272462431724919721011441141332022061874014076891267227202051062441493716183164104,56150782371065812687217214235135115253215613216622833513916825312441959074180196127",

        "Public": "OPTIONS,GET,HEAD,POST",

        "Timing-Allow-Origin": "*",

        "Date": "Sat, 22 May 2021 22:17:00 GMT",

        "Allow": "OPTIONS,GET,HEAD,POST",

        "Content-Type": "application/json; odata.metadata=full",

        "Expires": "-1",

        "Content-Length": "2044"

    },

    "body": {

        "@odata.context": "https://redacted.crm.dynamics.com/api/data/v9.1/$metadata#sharepointdocumentlocations(name,sharepointdocumentlocationid,relativeurl,_parentsiteorlocation_value,parentsiteorlocation_sharepointsite,locationtype,absoluteurl,parentsiteorlocation_sharepointsite())",

        "#Microsoft.Dynamics.CRM.DeleteSharePointDocument": {

            "title": "DeleteSharePointDocument",

            "target": "https://redacted.crm.dynamics.com/api/data/v9.1/sharepointdocumentlocations/Microsoft.Dynamics.CRM.DeleteSharePointDocument"

        },

        "@Microsoft.Dynamics.CRM.totalrecordcount": -1,

        "@Microsoft.Dynamics.CRM.totalrecordcountlimitexceeded": false,

        "value": [

            {

                "@odata.type": "#Microsoft.Dynamics.CRM.sharepointdocumentlocation",

                "@odata.id": "https://redacted.crm.dynamics.com/api/data/v9.1/sharepointdocumentlocations(5ba72aba-974b-eb11-a813-000d3a5a7103)",

                "@odata.etag": "W/\"33157354\"",

                "@odata.editLink": "sharepointdocumentlocations(5ba72aba-974b-eb11-a813-000d3a5a7103)",

                "name": "opportunity",

                "sharepointdocumentlocationid@odata.type": "#Guid",

                "sharepointdocumentlocationid": "5ba72aba-974b-eb11-a813-000d3a5a7103",

                "relativeurl": "opportunity",

                "_parentsiteorlocation_value@OData.Community.Display.V1.FormattedValue": "ACEServiceTechDev",

                "_parentsiteorlocation_value@Microsoft.Dynamics.CRM.associatednavigationproperty": "parentsiteorlocation_sharepointsite",

                "_parentsiteorlocation_value@Microsoft.Dynamics.CRM.lookuplogicalname": "sharepointsite",

                "_parentsiteorlocation_value@odata.type": "#Guid",

                "_parentsiteorlocation_value": "6851c8d7-0d2e-eb11-a813-000d3a5a7103",

                "locationtype@OData.Community.Display.V1.FormattedValue": "General",

                "locationtype": 0,

                "parentsiteorlocation_sharepointsite@odata.associationLink": "https://redacted.crm.dynamics.com/api/data/v9.1/sharepointdocumentlocations(5ba72aba-974b-eb11-a813-000d3a5a7103)/parentsiteorlocation_sharepointsite/$ref",

                "parentsiteorlocation_sharepointsite@odata.navigationLink": "https://redacted.crm.dynamics.com/api/data/v9.1/sharepointdocumentlocations(5ba72aba-974b-eb11-a813-000d3a5a7103)/parentsiteorlocation_sharepointsite"

            }

        ]

    }

}
 

 

The raw inputs are as follows:

{

    "host": {

        "connectionReferenceName": "shared_commondataserviceforapps",

        "operationId": "ListRecords"

    },

    "parameters": {

        "entityName": "sharepointdocumentlocations",

        "fetchXml": "\n  \n    \n    \n    \n    \n    \n    \n    \n      \n    \n  \n",

        "$top": 1

    }

}

 

We can see that when a previously created Power Automate Flow runs using the exact same code and points to the opportunity entity, it executes without issue.

Is this a bug or defect in Power Automate that was just introduced between May 2 and today or is there something else involved here that I need to address?