Could Not Determine Type Error

(0) Share

Report

Posted on by Serviced2000

172

Hi There,

I am trying to update a D365 entity row using a Power Automate flow. This update will connect one entity to another, but I’m not using the ‘Relate’ step as I don’t think it’s appropriate. I have overcome an error regarding a missing ‘segment’ that is mentioned here :

https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Resource-not-found-for-the-segment-issue-in-Power-Automate/ba-p/552837

But I’m now getting a message : “Could not determine type” during the update action.

I’m using the current CDS / Dataverse connector as far as I can tell. Can anyone point me in the right direction? I may have duplicated this post - apologies if so.

Thanks!

Categories:

Using connectors

I have the same question (0)

All responses (4)

Answers (1)

Serviced2000 172 on at

Like (0)

Report

Hi Everyone,

I should probably point out that I am trying to update a GUID lookup column - not sure if that will help at all?

Was this reply helpful? Yes No
ajayan 11 on at

Like (0)

Report

Could you share the screenshot of the attribute mapping? when you use the CDS (Current connector) to reference an attribute, it should be in '/{EntitySetName}/{RecordId}' format.
You can get the EntitySetName using metadata browser (in Xrm toolbox) or CDS webapi.

Was this reply helpful? Yes No
Serviced2000 172 on at

Like (0)

Report

This is how I'm mapping the attribute:

I have tried this way too:

But got the same "Could not determine type" error - the raw input for this last step is :

{
    "host": {
        "connectionReferenceName": "shared_commondataserviceforapps",
        "operationId": "UpdateRecord"
    },
    "parameters": {
        "entityName": "crimson_vacancies",
        "recordId": "6355d8bf-c58a-eb11-b1ac-002248155a1a",
        "item/mercury_agreementid@odata.bind": "/mercury_agreements/9f441588-6be3-ea11-a814-00224814f90e"
    }
}

Thanks!

Was this reply helpful? Yes No
Verified answer

Serviced2000 172 on at

Like (0)

Report

Hi Everyone,

Problem solved! I'm afraid to say it was a Rookie mistake (although I *am* a Rookie) - we have multiple environments and I was pulling data from one environment and attempting to update tables in another. Once I recreated the Flow in the same environment as the data I was pulling / updating, all went as expected. Thanks for all the input and apologies if I wasted anyone's time.

Was this reply helpful? Yes No