Hi,
I am using a Common Data Service for when a record is updated and it is pointing to a Dynamics CRM environment at the Opportunity entiity then it should just send an email to prove it it getting triggered, but the Flow never gets triggered.
I've created the exact same flow using the Dynamics update record trigger and this works fine.
I have a Flow Plan 1 so licensing shouldn't be the issue.
The Dynamics Opportunity entitiy seems to have auditing setup too.
Any ideas what's happened?
Thanks
Tom
still not solved
Hi @Anonymous,
Has your problem been solved?
If your problem has been solved, You could go ahead and mark the post as solved by clicking “Accept as Solution” so that this thread will be marked for other users to easily identify!
Best Regards,
Community Support Team _ Lin Tu
Hi @Anonymous ,
Yes agreed. Couldn't find any documentation around this.
You could push the relevant data into a temporary entity when an opportunity is created in CRM using a workflow. Then trigger the flow from the temporary entity. Once you had done your business logic then you could delete the temporary entity record.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.
Thanks
About a month ago I spun up a trial instance of CRM and this allowed me to successfully use the Common Data Service against the Opportunity entity.
Yesterday I tried to use the Common Data Service against the Opportunity Entity in our CRM Sandbox environment and this is when it doesn't work.
Reading that article I'm still not clear and it's nearly 18 months old.
Hi @Anonymous ,
Yes that is the issue.
There are some discussions about this in the below link.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.
Thanks
Thanks, make sense now.
However, when I go to Data > Entities the Opportunities entity is not in the list (which I guess is the problem).
Any ideas?
Hi @Anonymous ,
What I meant is check the data in CDS by logging into powerapps.com > Data > Entities
Open the entity and click data.
Thanks
I have tried with the environment set to both current and selecting the exact name. The entities is set to Opportunities and the scope to Organization.
When a field is updated and the Dynamics record saved the Flow is never called as there is never an event in the Flow History. Using the Dynamics Record Updated this is executing ever time.
Can you eleborate on what you mean by this please - "Also check the data is showing in CDS entity."
Is there anywhere to look for debug to try and troubleshoot this as there's literally nothing to go on and it doesn't really make sense as it's so basic.
Thanks
Tom
Hi @Anonymous
Make sure if the selected trigger requires an environment to be selected, then you can choose (Current), which will always use the database within the environment in which Microsoft Flow runs. If you want your flow to always trigger based on an event in a specific environment, select that environment.
You can use scopes to determine if your flow runs if you create a new record, if a new record is created by a user within your business unit, or if a new record is created by any user in your organization.
Please make sure all the settings such as environment and scope are set correctly.
Also check the data is showing in CDS entity.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up.
Thanks