Great video. I needed to trigger a flow when an appointment is added for a contact. Couldn't work out how to filter using regardingobjectidtype. Now I know. Thanks!
Hi @mikekarls529, thanks for the kind feedback. The blog post is benitezhere.blogspot.com/2021/04/trigger-cloud-flows-based-on-regarding-obect-type-Dynamics-365-Dataverse.html I double checked and I can browse to it fine.
@@mikekarls529 classic work restrictions😅 Thank you. I've had to temporarily pause on creating content in the last ~12 months due to change of priorities but hopefully soon I'll be back. I still have WTF content in my backlog. Have a great day and enjoy the rest of 2022.
Here's a challenge. I need to set a trigger when a new note is added to an incident, but only if that note is for a particular account. I followed the steps you had in this video and I don't see a regarding field for the account, even though the account field is visible on the same form. I've been told Notes are a different beast. Any ideas on how to create this type of a trigger?
@@ElaizaBenitez yes. The case form. There is an account field and then there is a notes section. I’m trying to set a trigger so that the flow only runs for one account.
The _When a row is added, modified, or deleted Dataverse trigger_ doesn't allow filtering on the navigation property. Bit of an explanation: The Note (primary table for the trigger) has a property known as objectypecode - type of entity with which the note is associated. This is further defined by Lookup Properties which point to the row of the entity of the objecttypecode. When querying the Web API, you can get to the case details of the note, and then to the account details of the case - this is achieved by filtering through what is known as "single-valued navigation properties." Querying through the Web API supports this type of filtering but unfortunately it's not supported in the _When a row is added, modified, or deleted_ Dataverse trigger.
Great video. I needed to trigger a flow when an appointment is added for a contact. Couldn't work out how to filter using regardingobjectidtype. Now I know. Thanks!
Hello,
thanks for the video. but what if the folder already exists, and I want to upload a second document?
How would you use this for something like when someone creates a new POST on the timeline?
Great video! I tried going to your blog but looks like the site is down - do you have a new link?
Hi @mikekarls529, thanks for the kind feedback. The blog post is benitezhere.blogspot.com/2021/04/trigger-cloud-flows-based-on-regarding-obect-type-Dynamics-365-Dataverse.html
I double checked and I can browse to it fine.
@@ElaizaBenitez Looks like my work is blocking it, I can get to it fine on my phone :) Looking forward to watching all your videos!
@@mikekarls529 classic work restrictions😅 Thank you. I've had to temporarily pause on creating content in the last ~12 months due to change of priorities but hopefully soon I'll be back. I still have WTF content in my backlog. Have a great day and enjoy the rest of 2022.
Is there away to work on not just the regarding entity table but the regarding fields itself in trigger conditions?
Are you referring to the "Filter rows" input field in the trigger of When a row is added, modified or deleted?
Here's a challenge. I need to set a trigger when a new note is added to an incident, but only if that note is for a particular account. I followed the steps you had in this video and I don't see a regarding field for the account, even though the account field is visible on the same form. I've been told Notes are a different beast. Any ideas on how to create this type of a trigger?
"even though the account field is visible on the same form" - what's the form you're referring to, is it the Case form?
@@ElaizaBenitez yes. The case form. There is an account field and then there is a notes section. I’m trying to set a trigger so that the flow only runs for one account.
The _When a row is added, modified, or deleted Dataverse trigger_ doesn't allow filtering on the navigation property. Bit of an explanation: The Note (primary table for the trigger) has a property known as objectypecode - type of entity with which the note is associated. This is further defined by Lookup Properties which point to the row of the entity of the objecttypecode. When querying the Web API, you can get to the case details of the note, and then to the account details of the case - this is achieved by filtering through what is known as "single-valued navigation properties." Querying through the Web API supports this type of filtering but unfortunately it's not supported in the _When a row is added, modified, or deleted_ Dataverse trigger.