Transcript:
0:00 [Music]
0:04 hi everyone in this video I'm going to
0:07 demonstrate an if true function and an
0:10 update record function in North52
0:14 and if true function takes two
0:17 parameters something to test and wants
0:20 to do if the test is passed
0:23 an update record function takes a
0:26 minimum of three parameters the entry
0:29 logical name of the record to be updated
0:31 the good of the record to be updated and
0:34 at least one change you want to make to
0:37 the record you can use cell attribute
0:40 functions to update as many fields in
0:42 the record as you want there are a
0:45 variety of different types of set
0:47 attribute functions depending on if you
0:49 are setting a simple text field a lookup
0:52 a party list or changing the status of a
0:55 record to demonstrate this I'm going to
0:59 create a formula that will set the
1:01 description field of a case to be the
1:03 content of an email but this will only
1:06 happen when that emails regarding fields
1:08 have been set to a case and the cases
1:11 description field is empty so we start
1:15 by creating a new formula we navigate
1:18 the settings iN52 formulas and then
1:21 click on the new button this formula
1:24 will be of type save perform action and
1:27 it will run on the email entity we leave
1:31 the event at create and update and set
1:34 the source property to be the regarding
1:36 field this means that the formula won't
1:38 trigger unless the regarding field was
1:40 set when the email was created or if it
1:43 was updated afterwards
1:47 the first step in the formula would be
1:49 to check if the regarding field contains
1:51 data so we start with an if true
1:54 statement we then use the contains data
1:58 function holding down the shift key when
2:01 we click on the name will bring up the
2:03 wizard we select the regarding field
2:05 from the source tab and then click
2:07 generate
2:13 emails can be connected at various
2:15 entities in dynamics 365 and we only
2:18 want to trigger this logic if the email
2:21 is connected to a case so we click on
2:23 the regarding field again and then add
2:26 type to it this gives us access to the
2:30 type of entity currently in that lookup
2:32 field and we can then check if this is
2:34 the case the entity logical name in
2:37 Dynamics 365 for a case is incident
2:40 which is why I am checking if the type
2:43 is incident we are now checking if the
2:47 emails regarding field contains data and
2:49 that is connected to a case however we
2:54 also need to make sure that the
2:55 description field of the case is also
2:57 empty before we can continue so we added
3:00 in another end and then we go back to
3:03 our functions we will now use that does
3:07 not contain data function again we will
3:10 hold on the shift key and click on the
3:12 function to bring up the wizard on the
3:14 source tab we open up related enter 1
3:17 scroll down and expand incident then we
3:21 expand attributes we selected the
3:24 description field from this list and
3:26 this will now give us access to the
3:28 description field on the connected case
3:32 this if true statement will now check
3:34 three conditions before execute any of
3:37 our instructions one the regarding field
3:40 has to contain data to the regarding
3:43 entity has to be of type incident aka
3:46 case and 3 that case this description
3:49 field has to be empty it is worth
3:52 mentioning here that Noor 52 if and if
3:55 true statements execute their conditions
3:57 left to right and stop on the first fail
4:00 so if the regarding field is not set
4:03 then North52 won't worry about checking
4:06 the regarding object type or the cases
4:09 description etc now that we have all our
4:12 checks setup we need to actually update
4:15 the case with the content of the email
4:17 we will use an update record function
4:20 for this I can manually create an update
4:23 record function and fill in all the
4:25 details myself
4:26 or I can navigate to the Explorer tab
4:28 search for case expand the list of
4:32 attributes and then take the box for the
4:34 description next I use the update record
4:37 builder as you can see the framework for
4:41 the update record function has been
4:42 added to the formula canvas as I
4:45 mentioned earlier an update record
4:47 function will need a minimum of three
4:49 parameters the first one is the logical
4:52 name of the record to be updated in this
4:55 case incident the second one is the good
4:58 of the specific record to be updated the
5:01 builder has by default enter the value
5:03 we will delete this as we know the
5:06 specific record we need to update is
5:08 stored in the regarding lookup on the
5:11 email so we go back to the source tab
5:14 and select it from there
5:16 the last parameters in an update record
5:19 are the actual changes you want to make
5:21 to your record in this case you can see
5:23 there's a set attribute function set for
5:26 the description field we will delete the
5:29 default value again and they could just
5:31 select description from the source tab
5:33 however many email messages come with
5:37 HTML formatting applied to them and I
5:40 don't want any of that bleeding into the
5:41 cases description field
5:43 so I just take all that out and I search
5:46 for the strip HTML function and then
5:49 hold down the shift key and click on the
5:52 function name this will open the formula
5:54 wizard I then select the email
5:57 description field as the input string
5:58 click generate and save my formula
6:03 on this screen I have a test email
6:06 created I use the convert button to
6:09 convert this into a case and then select
6:11 my customer when this case has been
6:14 created you can see that the description
6:15 has been copied over
6:20 thank you for watching and as always if
6:23 you have any questions or need any
6:24 assistance please contact support at
6:27 Noir 52 comm or visit support noir 52
6:30 calm