Transcript:
0:00 [Music]
0:05 hi everyone this is Patrick from North
0:07 52 here and today we are going to take a
0:10 look at the scheduler in North52 with the
0:13 North52 scheduler you can trigger
0:15 workflows and actions over specific
0:17 subsets of Records or all records in
0:20 your
0:22 system this series will be broken into
0:24 several videos where we will first get
0:27 familiar with the schedular interface
0:29 then we will set up a basic schedule to
0:32 send a happy birthday email to all users
0:34 in a dynamic system next we will look at
0:38 understanding some of the more advanced
0:40 fields found in a schedule then we will
0:43 set up a daily email notification to a
0:45 system administrator for failed system
0:48 jobs and then finally we will talk about
0:50 how the N52 scheduler can handle huge
0:53 quantities of Records while still
0:55 maintaining excellent performance in
0:57 your Dynamics 365 environment
1:01 to get to the schedules we first
1:04 navigate to settings n52 schedules and
1:08 then click on new to create a fresh
1:10 one the first step would be to name your
1:13 schedule then we specify the frequency
1:16 of the schedule you can set it to run
1:19 hourly daily weekly monthly yearly
1:23 quarterly or every X number of them
1:27 please bear in mind that while you can
1:29 set it to repeat every X minutes as well
1:32 Microsoft won't allow a schedule to
1:35 execute more than once per hour so if
1:37 you try and Trigger it every 1 minute
1:40 don't be surprised when you see it only
1:41 firing every hour
1:45 instead you must then select what type
1:47 of schedule you want to run there are
1:50 three options workflow Global action or
1:54 entity update a workflow schedule will
1:57 trigger a workflow a global action
1:59 triggers the global action an entity
2:01 update though is slightly different
2:04 instead of firing something the schedule
2:06 will instead nudge that entity and
2:08 Trigger any plugins on it you can
2:10 control which fields on the entity are
2:12 triggered by using the fetch
2:16 XML you then set the start date when you
2:19 want the schedule to fire first and if
2:22 you set the frequency as daily it would
2:24 fire again 24 hours later for workflow
2:28 and entity update style schedule
2:30 you would need to enter fetch XML that
2:32 will be used to identify the set of
2:34 Records you want the schedule to run
2:36 against the fetch XML must be valid if
2:39 you enter junk you will then get an
2:41 error message when you try and
2:45 save when the schedule has been created
2:48 like this the next step is to actually
2:50 start the schedule so click on n52
2:54 commands start schedule this will create
2:57 an instance of the N52 schedule in your
3:00 system
3:01 jobs you can see this by navigating to
3:04 settings system
3:07 jobs select n52 schedule in the entity
3:11 dropdown you will see a waiting instance
3:13 of the system job and any successes or
3:16 failures if you are keeping
3:20 them if you ever want to stop a schedule
3:23 return to the schedule and then use n52
3:26 command stop schedule
3:33 in the next video we will configure the
3:35 happy birthday schedule thank you for
3:37 watching and if you have any questions
3:39 please contact support at North52.com
3:42 or visit support. 52.com