Microsoft Dynamics 365 | Integration, Dataverse...

Recurrence Pattern - how to process records generation?

(0) Share

Report

Posted on by EBMRay

905

Hello,

I would like to build a recurrence functionality that is very similar to the Agreement Booking Setup -> Booking Repeat functionality, which is the following:

The purpose of this feature is to avoid manual intervention if I have a task that repeats frequently. Here is an example:

Example: I want to add 3000$ bonus for 10 employees for 3 months which means each month an employee will earn 1000$.

Instead of going for each employee and adding 3x records per employee manually, the manager can select the employees and schedule the Bonus installment for each individual.

The recurrence will not just be monthly as we need to have the Weekly,Quarterly, Annually units.

What do you suggest as a solution to achieve the above requirements and could you please clarify how the records will be processed? Which product shall be used for the development process?

Any help is greatly appreciated.

Best regards,
EBMRay

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Haig Liu Microsoft Employee on at

Like (1)

Report

Hi,

There are no any OOB settings can be achieved it.

Maybe you can try to use power automate to create scheduled flows:

https://learn.microsoft.com/en-us/power-automate/run-scheduled-tasks

In the fields next to Repeat every, specify the flow's recurrence.

Was this reply helpful? Yes No
EBMRay 905 on at

Like (0)

Report

Hello Haig Liu ,

Thank you for your reply.

Exactly, this is why we want to build it from scratch.

Power Automate will not help us in specifying the recurrence parameters because it is static. If I want to proceed with this option, I would create x numbers of workflows for each scenario.

The requirements are more extensive than this since the user will be able to choose the recurrence units parameters dynamically and the magic should happen via either Power Automate or Azure Logic Apps or Azure functions.

At a high level, we would need one table for "Reoccurence setup", another table for "Records generation".

For instance, if I want to give a Bonus to an employee every Sunday and Tuesday without an end date, how would we handle it?

As far as I know, in the flow we can check the dayofweek, etc., but what about records without an end date?

2. Another one is the End date behavior can also be set after a certain number of occurrences.

3. Another one can generate a record every X days and only on weekdays etc..

The same as the above example but for X number of occurrences only. (It might be 4,3 or whatever..)

In your opinion, what do you suggest regarding the structure of the tables and what would be the workflows to handle any Unit logic dynamically + end date behavior scenarios?

How might we structure it in an effective manner?

Appreciate your assistance and I will be awaiting your feedback.

Was this reply helpful? Yes No
Suggested answer

Leah Ju Microsoft Employee on at

Like (2)

Report

Hi EBMRay,

When you set the scheduled flow, you can choose any day or days of the week:

For your question: but what about records without an end date?

You can refer the following video to know how to stop the scheduled flow automatically(Set and check the end date directly in the conditions of the process.):

https://www.youtube.com/watch?v=sq8lbCrCyeE

Was this reply helpful? Yes No
EBMRay 905 on at

Like (1)

Report

Hello Leah Ju ,

Thank you for your reply.

The option that you suggested will not work with us because the "Scheduling occurence interface" should be accessible from model-driven and an HR user will be choosing dynamically how frequently that should operate.

Sometimes weekly, monthly, annualy, semi-annualy and the HR user will not know on how to create a workflow.

As a result, we need to consider how we are going to create the setups tables, allowing the user to pick out his desired occurrence, and then the magic should occur in the back-end to process the data records.

I hope my point is clear and if not, I would be happy to give more details.

I will be waiting for your response.

Best regards,

EBMRay

Was this reply helpful? Yes No
richardpanek 20 on at

Like (0)

Report

Hi EBM Ray,

I'm in the same boat looking for the same thing you are and understand it isn't possible in a Scheduled Flow. Did you find anything?

Right now it looks like I might be needing to create a daily task that looks through all the records in a field where you set the re-occurrence (bi-weekly for example) and then look at a 'last scheduled' value and then programmatically hardcode some logic for each dropdown value (bi-weekly, every weds, yearly) etc. Then generate a new record from that logic in a dynamic window.

This would be a lot of work so hoping something else has a better suggestion

Was this reply helpful? Yes No