Transcript:
0:00 [Music]
0:04 hello everyone this is Patrick from
0:06 North52 and in this video I'm going to
0:10 go through some of the bugging and
0:11 tracing that's available in North52 to
0:15 do this we have a simple formula that is
0:17 hooked up to the opportunity entity
0:19 whenever the estimated value or the
0:22 close probability on an opportunity
0:24 change it will execute a smaller
0:27 calculation and store the output in the
0:29 description field
0:31 the formula will first check if the
0:34 estimated value contains data then it
0:36 will multiply that estimated revenue by
0:38 the cause probability and divide the
0:40 outcome by 100 this gives us our awaited
0:43 estimated revenue value that is then
0:45 stored in the description field as you
0:49 can see this is a very simple formula
0:51 its sole purpose is to give you an
0:53 understanding the debugging and tracing
0:55 that is available in noir 52
0:58 on this tab I have an open opportunity
1:00 it's estimated revenue is set to eight
1:03 thousand four hundred and eighty seven
1:04 pound sterling when I changed the flow
1:07 of probability to say 20 percent and
1:10 click Save you can see now that the
1:13 description field is populated one
1:15 thousand six hundred and ninety seven
1:17 pounds and forty pence would be the way
1:19 to the estimated revenue now
1:21 this is a very simple formula but for
1:24 example if the calculation was a little
1:26 bit more complicated and it was not
1:28 producing the output you were expecting
1:30 we would need to turn on tracing in the
1:32 formula to see exactly what happens at
1:34 each step in that formula
1:36 we will turn on tracing here at the
1:38 formula level on the register tab we
1:41 expand the deployment settings node and
1:44 then select information from the drop
1:46 down list
1:47 this instructs the formula to produce a
1:50 trace log whenever it executes in the
1:52 dynamics instance this will give us a
1:55 clear picture of what happens in this
1:56 formula real time including any outputs
1:59 from not 52 function calls and any
2:02 values that we used during the
2:03 calculation I will now trigger the
2:06 formula again by increasing the
2:08 probability to 70% and clicking save the
2:11 value in the description field changes
2:13 again and we will now click back to the
2:15 formula and open the formula trace tab
2:17 you can see that a trace lock has been
2:20 created so we'll open it and take a look
2:22 at its contents
2:26 like that is generated is linked to its
2:28 parent formula you can see the date and
2:30 time it executed as well as the user
2:32 involved the trace will contain all
2:34 information about the formula as the
2:36 execute through the dynamics instance
2:39 the trace log is broken into multiple
2:41 sections the first of these is the
2:43 plug-in context here we can find
2:45 information about the message in this
2:48 case there was an update message that a
2:50 create or delete message etc the stage
2:53 is 40 which means it's a post operation
2:56 stage so the change that trigger the
2:58 formula has already been committed to
2:59 the database
3:01 the depth is one Microsoft uses depth to
3:04 control infinite loop depth in logic and
3:07 dynamics for online instances Microsoft
3:09 allows a depth of up to 16 or on-premise
3:12 they allow 8 by default or 9 premise
3:15 instance though you can raise the level
3:17 using PowerShell commands that is not
3:19 available for online instances the next
3:22 section is the entity trace for the
3:24 opportunity these are the values that
3:26 were changed on the record and then
3:28 saved the safe to the database trigger
3:30 this formula you can see the clothes
3:32 probability was changed to 70 and the
3:35 modified on a modified by were also
3:37 changed this is an automatic
3:38 functionality by Microsoft where no
3:40 record gets water played
3:43 at the end of the plugin context
3:45 information you can see the list of
3:47 formulas to be triggered in this case
3:49 it's only one formula with a shortcode
3:50 of seven bi and the input for the
3:53 formula are the fields estimated value
3:55 opportunity ID and the closed
3:57 probability the opportunity ID is an
4:00 input since we'll be using this value to
4:03 complete an update statement on the
4:05 opportunity with the output of the
4:06 calculation
4:08 the next part is the execution of each
4:10 of the formulas that are triggered and
4:11 their outputs each formula has a start
4:14 and an end so if you have multiple
4:16 formulas executing it is easy to trace
4:19 exactly what each one is doing as the
4:23 formula executes you will see an output
4:25 for each function that's called ignore
4:27 52 you can see here the first one is the
4:30 output from the contains data which has
4:32 a value of true since the estimated
4:34 revenue contains data
4:37 next you can see the setattribute
4:39 function it's populated with the output
4:42 of the calculation ensure that it would
4:44 be a value put in the description field
4:47 the output of the update record function
4:49 tells us that an opportunity record with
4:52 this good was updated since North52
4:55 formulas pass the results out each time
4:57 the result of the if true is the good
5:00 and then the results of the decision
5:02 table is the Google as well you can read
5:04 more about this in the link to our
5:06 support article entre slug reading in
5:08 the comments below
5:10 finally the next relevant piece is the
5:13 entity trace for the norm fifty two
5:14 formula itself this gives you
5:16 information about the shortcode the
5:18 entry name and the attributes that the
5:20 formula is connected to its pipeline
5:23 stage post-op pre-op etc and the formula
5:25 type
5:27 this can be especially helpful when you
5:28 have multiple chains of formulas
5:30 executing for example the updated
5:32 description field might trigger another
5:34 formula that updates something on the
5:36 primary account which in turn might
5:38 trigger a formula on the account in
5:39 three this section in the trace log will
5:42 give you information about that formula
5:45 this video provides a very high-level
5:46 overview of debug and trace capabilities
5:49 in norm 52 if you would like to know
5:52 more we have detailed information
5:53 available on our support site thank you
5:57 for watching and as always if you need
5:59 any assistance please visit
6:00 support.norton.com or email support at
6:04 North52 comm