Unanswered

Dataverse Trigger with Object Type Filter

(0) Share

Report

Posted on by HerrMueller

Hi,

I want to have a flow triggered when adding a new row to a table in the dataverse. The flow should also only trigger when a lookup (regardingobjectid) is of a defined type, in this case "bookableresourcebooking".

I tried some things, but the trigger always shows errors..

_objectid_type eq 'bookableresourcebooking' results in Microsoft.OData.ODataException: Could not find a property named '_objectid_type' on type 'CallbackRegistration.annotation'

_objectid_value@Microsoft.Dynamics.CRM.lookuplogicalname eq 'bookableresourcebooking' results in Microsoft.OData.ODataException: Syntax error at position 56

Any idea how to achieve this?

And yes, I know I can filter the object type in a condition afterwards, but I don't want the flow to be triggered at all.

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Expiscornovus 33,189 Most Valuable Professional on at

Like (1)

Report
Hi @HerrMueller,

I believe there should also be a field called objecttypecode. Can you try and use that in your filter?

objecttypecode eq 'bookableresourcebooking'

Was this reply helpful? Yes No
Riyaz_riz11 3,844 Super User 2025 Season 2 on at

Like (1)

Report
Hi @HerrMueller

You can try this.

objecttypecode eq 'bookableresourcebooking'

Regards

Ahammad Riyaz

--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Was this reply helpful? Yes No
HerrMueller 79 on at

Like (0)

Report

Oh yeah, ok in this scenario this helps out. Thanks for that!

But do you have any idea what I can do if I want to filter the lookup object type for filter, if this field is not in place? E.g. for activity entities and regarding field?

Was this reply helpful? Yes No
Riyaz_riz11 3,844 Super User 2025 Season 2 on at

Like (0)

Report

@HerrMueller You can use filter array as well to filter the data.

Once if works please mark as a solution so others will get help for same query.

So better you can post next question for separate requirement.

Regards

Ahammad Riyaz

--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Was this reply helpful? Yes No
Verified answer

Expiscornovus 33,189 Most Valuable Professional on at

Like (3)

Report
Hi @HerrMueller,

I have seen multiple threads where the trigger action did not like the regardingobjectid type column in the OData filter. That one is a bit more challenging.

You could try using a trigger condition as a workaround instead of a OData filter rows field. Add something like below in the settings of your trigger action:

@equals(triggerOutputs()?['body/_regardingobjectid_value@Microsoft.Dynamics.CRM.lookuplogicalname'], 'bookableresourcebooking')

Was this reply helpful? Yes No