Dynamics 365 is a portfolio of intelligent business applications that delivers superior operational efficiency and breakthrough customer experiences enabling businesses to become more agile and reduce complexity without increasing costs.
Changelog
9 versions
v2.2.0
Latest
- Added polling triggers: New Contact, Updated Contact, New Lead, Updated Lead, New Account, Updated Account, New Object Record and Updated Object Record. They detect created/updated records by polling the Dataverse OData API on createdon/modifiedon, deduplicate by record id and start watching from the moment the flow is started (historical records are never emitted). The New/Updated Object Record triggers work with any (including custom) entity via the same entity selector as the Object Record actions.
- Added the 'Deal Stage Changed' trigger: fires when the sales stage of an opportunity changes. It remembers the stage of each opportunity it has seen and fires only on an actual stage transition (the watched stage attribute is configurable, defaulting to 'salesstage').
- Create/Get/Update/Delete Object Record (and the generic Object Record triggers) now resolve the entity collection segment from the Dataverse metadata instead of naively appending 's' to the logical name, so entities with irregular plurals (e.g. opportunity -> opportunities) work too.
- MakeApiCall: the Request Headers and Query Parameters key-value inputs are also accepted as a JSON string (e.g. when produced by a flow transform).
v2.1.1
- CreateObjectRecord/UpdateObjectRecord: lookup fields (e.g. regardingobjectid, transactioncurrencyid) are bound via their target-specific navigation property and are no longer marked as required in the inspector — they use navigation-property names rather than the bare logical name and are commonly auto-populated by the Web API, so requiring them blocked otherwise-valid configurations.
- ListEntities: the output variable picker now adapts to the selected Output Type (array / object / file) instead of always showing the array shape.
- UpdateObjectRecord/UpdateAccount/UpdateContact/UpdateLead: the inspector-generation source now wires the required objectName/id inputs (and the schema declares its properties), so inspector generation is no longer rejected by required-input validation.
v2.1.0
- Added the 'List Entities' component to retrieve all entities (object types) in the organization.
- CreateObjectRecord/UpdateObjectRecord: the Object Name field is now a typeahead that suggests the most common entities while allowing any entity logical name to be typed manually (or bound from the new 'List Entities' component).
v2.0.0
- (breaking change) MakeApiCall: headers and parameters changed to key-value array inputs (body remains textarea/JSON to support nested structures) per standard #1459 — existing flows that used the old string/textarea headers or parameters must be updated
v1.0.7
- Added output examples to component schemas.
v1.0.6
- The authentication flow now displays an account selection screen.
v1.0.5
- Connection can now be created with custom tenant. To see the option while creating the connection, in the Admin -> Connector Configuration add configuration 'appmixer:microsoft' and inside it, add item 'microsoftTenant' and set its value to true.
v1.0.4
- Fix for possible connection with empty label.
v1.0.3
- Initial release
Authentication
| Type | Details |
|---|---|
| OAuth 2 |
Authentication Hub
Verified
This connector is globally authenticated and verified by Appmixer and is ready to use without registering your own OAuth application with the provider. Appmixer's Authentication Hub acts as an authentication proxy, so all OAuth-based connectors work out of the box. You can still use your own OAuth credentials (clientId and clientSecret) for enhanced customization or compliance — see the Connector Configuration section of the documentation. The Authentication Hub is enabled for all hosted Appmixer tenants; on self-managed installations it has to be explicitly set.
Scopes:
offline_access
|
Triggers
9
Deal Stage Changed
Triggers when the sales stage of an opportunity (deal) changes in Microsoft Dynamics 365. The trigger remembers the stage of each opportunity it has seen and fires only on an actual stage transition - creating or editing an opportunity without changing its stage does not fire it.
New Object Record
Triggers when a new record of the selected Entity type is created in Microsoft Dynamics 365. Works with any entity, including custom ones.
Updated Object Record
Triggers when a record of the selected Entity type is updated in Microsoft Dynamics 365. Works with any entity, including custom ones.
Actions
21
Create Object Record
Creates a new object based on Entity type you select using API v9.2. Object attribute names are localized and available in the language of your account.
List Entities
Retrieve the list of entities (object types) available in your Dynamics 365 organization. Use the 'Logical Name' output as the Object Name in other components.
Update Object Record
Updates an existing object based on Entity type you select using API v9.2 and HTTP method PATCH. Object attribute names are localized and available in the language of your account.