Given that we're moving feedback data from one CDS to Dynamics 365, we will need the feedback entity created in both platforms. The Dynamics 365 entity does not have to exactly match the CDS one; however, some degree of attribute compatibility is required. For example, the sentiment can be a picklist in the CDS, but in Dynamics 365, it may be a text field.

In addition to the platform's schema, you will need the correct license to be able to create and use a Flow process. Flow can be purchased independently or bundled with Dynamics 365 Plan 1 or higher. Finally, the user used to create a record in Dynamics 365 must have created privileges on the Feedback entity in Dynamics 365.