Share your ideas and vote for future features

Currently for dynamics we can trigger a flow when an entity is created/deleted/updated, but for updates we aren't able to determine which fields changed. It would be nice to have the ability to trigger only on certain fields changing, or at the very least have some common triggers like when a Lead is assigned, for example. ... View more

Add way to work with N:N relation for CRM entities ... View more

I'm not able to perform actions on connections between records/users in CRM. I'd like to be able to update a record to change the owner to whom it is assigned. A standard REST Update action cannot make changes to fields that are read only (foreign keys cannot be changed directly). Other actions, like add to queue are also needed. Queue is another field that cannot be changed directly. ... View more

Hi,   I Would like to close an opportunity in CRM automatically when the expected close date has been pased. We have al lot of old opportunities in CRM, and we are creating new onces with a flow when a e-mail has been received. Therefor I would like to build a flow that will automatically close this opportunities. I tried to do this with the update a record but have no been able to arrange this. ... View more

  I'm trying to create a flow to automatically add a new support cases to a queue in Dynamics CRM. I'm able to create QueueItem from the new Case, and I can look up the Queue by name, but I don't see a field on either record relating to the other (no QueueID field on the QueueItem, no QueueItems field on the Queue). There should be some linkage to indicate to which queue to add the QueueItem.   Alternatively, an action to Add CRM record to queue could be useful to increase clarity to business users.   [edited to add]: More specifically, we should be able to perform any of the actions provided by the Dynamics 365 WebAPI, inlcuding assign to queue ... View more