You’re offline. This is a read only version of the page.
1,710
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,
Julien
Hello @EricRegnier ,
Appreciate all your answers.
You are definitely right I will give it a try and start development. I will get back to you with an update when I generate the first output result.
Best regards,
Julien
HI @Julien2, one other thing I wanted to recommended is to just go ahead and give it a try. Inspect, adapt and improve afterwards. Sometimes we tend to try build a perfect solution, and think of all the possible scenarios when sometimes can be overkill. The key is to keep it simple with future proofing in mind without necessary catering right away for all scenarios:)
I think next refresh data is optional, it all depends how you want the logic. It can run daily (or several times) a day and then determine if the conditions to create are valid based on the last run date. Or you check the condition against next refresh date but note you still need to check that the last run date >= next refresh date to ensure its doesnt fire more than once between intervals...
Hello @EricRegnier ,
Please accept my sincere thanks for your detailed responses.
To summarize, I just created a very simple excel sheet and added a sample row for the "Record Creation Configuration table" as follows:
I think we were missing the column "Next refresh date" (highlighted in bold in the above screenshot) on the record creation where on daily basis at 6:00 AM the flow is checking if the record should be generated and comparing it to today's date. If they are equal -> generate the record -> update the next refresh date based on the number of days specified (in the example they are 3).
I believe the next refresh date for any unit will achieve the requirement.
Another complex example is an occurrence that occurs on certain days repeat every monday and friday so on monday if the record was generated it will add to today's date 4 days (Monday until Friday) and that will be updated in the "Next refresh date" column and then when it reaches "Friday" it will add 3 days for the next "Refresh date". (Friday until Monday)
The challenge is how are we going to split it into child flows in a logical sense.
Do you agree with the above? I'm doing some brainstorming before I start the real-testing.
I would highly appreciate your input.
Best regards,
Julien
Hi @Julien2, apologies for my late reply. Here are answers to your questions following your numbering:
Hope this helps!
Hello @EricRegnier ,
I would highly appreciate it if you had the chance to check my reply.
Best regards,
Julien
Hello ,
I took the recurrence pattern screenshot from the field service module and yes it is not included as OOB if you want to implement it for your custom model-driven app as we need to build it from scratch.
If I want to give a Bonus to an employee every Sunday and Tuesday with no 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.
The same as the above example but for X number of occurrences only. (It might be 4,3 or whatever..)
In your opinion, do you think that one cloud flow will be huge to handle all of the logic? Shall we have different child flows and each will be checking on a different repeat unit + end date behavior scenarios?
If so can you suggest how we may structure it in a more effective way?
Appreciate your assistance and I will be awaiting your feedback.
Best regards,
Julien
Hi @Julien2,
As for which product used, I assume you mean Dynamics 365 apps? If so I'm not sure there's anything that comes out-of-the-box to achieve this... But this requirement can be done with a mix of Dataverse and Power Automate. At a high-level I would have something like:
Hope this helps a little!
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
17
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
