cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Serviced2000
Helper II
Helper II

Could Not Determine Type Error

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...

 

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!

1 ACCEPTED SOLUTION

Accepted Solutions
Serviced2000
Helper II
Helper II

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.

View solution in original post

4 REPLIES 4
Serviced2000
Helper II
Helper II

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?

ajayan
Frequent Visitor

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.

ajayan_0-1616453731912.png

You can get the EntitySetName using metadata browser (in Xrm toolbox) or CDS webapi.

Serviced2000
Helper II
Helper II

This is how I'm mapping the attribute:

 

Serviced2000_0-1616454548480.png

 

I have tried this way too:

 

Serviced2000_1-1616454586997.png

 

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!

 

Serviced2000
Helper II
Helper II

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.

View solution in original post

Helpful resources

Announcements
Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

Users online (38,619)