web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Does the prospect to c...
Power Apps
Unanswered

Does the prospect to cash scenario works as planned?

(0) ShareShare
ReportReport
Posted on by

What do I mean?

We are using the common data model to feed other system with the "When a record is updated"-trigger in Logic Apps.
We are getting data into the CDS with the prospect to cash scenario (synchronise data between D365fO and the CDS).
So far so good.

 

My expectation is:

  1. When I change in D365fO one record, after synchronisation CDS mark it as modified
  2. When I dont change records in D365fO, after synchronisation CDS information aren't updated (not modified)

What really happens:

Everytime I start the sync all CDS records will be mark as modified, but I haven't changed them.

 

This leads me to the question..

..do I misunderstand the common data model/service?

 

 

Kind regards,

Birk

Categories:
I have the same question (0)
  • v-monli-msft Profile Picture
    on at
    Re: Does the prospect to cash scenario works as planned?

    Hi @Anonymous,

     

    Can you share your detailed configuration of the Flow triggred by the app?

     

    Also, you cannot actually synchronise data between D365fO and the CDS as this is 2 way thing but flow can only do it one way.

     

    Regards,

    Mona

  • Community Power Platform Member Profile Picture
    on at
    Re: Does the prospect to cash scenario works as planned?

    Hey @v-monli-msft,

     

     

    I agree with you that the CDS can only "export" data via flows, thats clear so far.

    The foreign/third party system would e.g. generate a new record directly on D365fO (via OData), so next sync would push the data into CDS.


    But my message was about the export trigger "When a record is updated" itself, which mark existing record in the CDS as modified when the synchronisation is running. But I don't change any record on D365fO side.

     

    My setup:
    01Task

    01Task
    02Connection
    02_Connection
    03Execution1of2
    03_Execution1of2
    03Execution2of2
    03_Execution2of2

     

    What I additonally can say the modified timespamp in the data view of the vendor entity, was set to the time of sync.
    That implements that the trigger would run for each record although no one record was modified in D365fO.
    So I would give you some overviews of the logic app and the execution but this stupid project killed my whole MSDN credit for Azure.

    If you need a more detailed description let me know.

    Thank you for your feedback, Mona!

    Kind regards,
    Birk

  • Community Power Platform Member Profile Picture
    on at
    Re: Does the prospect to cash scenario works as planned?

    I got a response of the PRINCIPAL PROGRAM MANAGER of Microsoft in another forum:
    "Prospect to Cash uses bulk APIs to upload data. So, it avoids the trigger logic by default. We can enable this but have not currently done so."

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 757 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 322 Super User 2025 Season 2

#3
MS.Ragavendar Profile Picture

MS.Ragavendar 209 Super User 2025 Season 2

Last 30 days Overall leaderboard