Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested answer

Staging approach suggestion

(0) ShareShare
ReportReport
Posted on by 10
Hi
 
I am trying to find a proper approach for a scenario.
Here is the scenario: Enquiries come into the system from different geographies and each geography has its own processing logic. For example, an enquiry from Vietnam has a different contact matching logic compared to an enquiry from European countries. There is other processing logic that differs based on other parameters. 
I am also looking at storing the incoming records for a specified duration for auditing purposes.
 
I am looking at using staging pattern where all incoming records are stored in a custom entity. A scheduled process then processes records from the custom entity based on certain flags and parameters. I am stuck at identifying how and where the processing logic has to be added and invoked from within the scheduled process. The scheduled process could be a scheduled task on a windows server.
 
Can someone please point me in the right direction? 
  • Suggested answer
    Fubar Profile Picture
    Fubar 2,752 on at
    Staging approach suggestion
    Not sure why you would run it on a schedule, you could just trigger it on create of a record and not have the delay of waiting for the schedule.  For schedule use Power Automate Flow or Logic Apps, for triggering on create of record use Plugin, Workflow, or Power Automate Flow.
     
    Also, it is unclear how the enquiry is being made, is it via email, a portal form, someone manually creating a Case etc? how do you know what geography it is coming from? and what Dynamics 365 Customer Service components are you using? the answer these may influence the answer.
    e.g. you may have things available such as Queues configured for different incoming email addresses (i.e. email address for each geography tied to a queue for that geography), Case Routing Rules. 
  • Suggested answer
    PerezAguiar Profile Picture
    PerezAguiar on at
    Staging approach suggestion
    Hey
     
    Are we talking Dynamics 365 here? If that's the case, then you can have a custome entity (or Custom table) that stores all the data.  Then use PowerAutomate to trigger whenever records are added to this particular table, and based on the fields populated, perform the operation (insert records in another table, update fields, etc)
     
    However, you can also follow same logic for incoming emails/records in another entity.  For example: "Enquiries from Vietnam" could be a PowerAutomate that checks the Case table (or any other), and then perform the specific logic/steps that you intend to use.  Then, a second PowerAutomate "Enquiries from EU" can be created just for the correct purpose.  You can either use the "when a record is created/added" trigger (in case you want to process all records as they are created), or execute these automations on a specific schedule (every 5 mins, every 1 hr, etc)
     
    Regards,

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,375 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans