Power Automate: Difference between revisions

Jump to navigation Jump to search

Power Automate (view source)

Revision as of 10:19, 23 February 2023

1,449 bytes removed ,  23 February 2023
→‎Use case: Migrate models and equipment from Dynamics to resco.Houston: del
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.}}
[[File:Create Houston Equipment flow.png|thumb|right|Create Houston Equipment flow]]
[[File:Update Houston Equipment flow.png|thumb|right|Update Houston Equipment flow]]
Resco Cloud connector can be used to connect Dynamics and [[resco.Houston]]. We are matching the following entities:
{| class="wikitable"
! Dynamics || Houston
|-
| Product (product) || Model (rh_model)
|-
| Customer Asset (msdyn_customerasset) || Equipment (fs_asset)
|}
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.
Out of the box, none of these flows modify any records on the Dynamics server; this is a one-directional transfer.
You can modify the templates to better match your needs, potentially adding custom fields to the mapping as needed.


== See also ==
== See also ==
Retrieved from "https://docs.resco.net/wiki/Special:MobileDiff/8496"

Navigation menu