9,275
edits
Join the Power Platform Masterclass #2 starting April 23
Power Automate: Difference between revisions
Jump to navigation
Jump to search
→See also
(→FAQ) |
|||
| Line 149: | Line 149: | ||
Now, when you create a record of the specified entity type, the trigger activates. | Now, when you create a record of the specified entity type, the trigger activates. | ||
== Use case: Migrate models and equipment from Dynamics to resco.Houston == | |||
{{Note|The connector updates described in this section have been submitted to Microsoft and are waiting for approval.}} | |||
Resco Cloud connector can be used to connect Dynamics and [[resco.Houston]]. We are matching the following entities: | |||
{| class="wikitable" | |||
! Dynamics || Houston | |||
|- | |||
| Product || Model | |||
|- | |||
| Customer Asset || Equipment | |||
|} | |||
The connector includes three sample flow templates related to resco.Houston: | |||
* Houston migration - a one-time manual migration of models and equipment. Takes all Dynamics records and copies them to resco.Houston. | |||
* Create Houston Equipment - an action triggered by a change in Dynamics. When a Customer Asset record is created, the asset and its parent product are transferred to resco.Houston. | |||
* Update Houston Equipment - an action triggered by a change in Dynamics. When a Customer Asset record is updated, the asset and its parent product are updated in resco.Houston. | |||
None of these actions | |||
== See also == | == See also == | ||