1
00:00:01,660 --> 00:00:02,220
Fence.

2
00:00:02,360 --> 00:00:07,660
So welcome to yet another session on success factors here and we'll be discussing about the differences

3
00:00:07,660 --> 00:00:15,220
between the two parties and much cause with which both of which are type of deep because one of the

4
00:00:15,220 --> 00:00:21,060
difference that we saw in the previous sessions about the representative it has been that if you execute

5
00:00:21,070 --> 00:00:34,300
and replace bond then all the values of the fees which are there in the request body are replaced by

6
00:00:34,300 --> 00:00:38,020
the values which I did identify the values.

7
00:00:38,050 --> 00:00:44,350
So the back and values of all those speeds which are dated Rick's party are replaced by values which

8
00:00:44,350 --> 00:00:50,050
we have posited that call if there is a desert in fields which are not dating the request body they're

9
00:00:50,150 --> 00:00:58,480
either placed as null value blank values or they are either placed back to their defined values based

10
00:00:58,480 --> 00:01:01,930
on the setting set up there for those particular fields.

11
00:01:01,960 --> 00:01:12,300
Now here one might be tempted to understand this as being an object is being created every time when

12
00:01:12,350 --> 00:01:19,960
if this call is made that is you make a call to the place you make that it baseball then that particular

13
00:01:20,320 --> 00:01:26,520
object of those pretty keys is basically diluted and a new object is being created.

14
00:01:26,530 --> 00:01:32,270
So this might be it might be a temptation for us to think from the conceptual perspective that this

15
00:01:32,270 --> 00:01:34,330
is what is undergoing these back end.

16
00:01:34,600 --> 00:01:36,440
So let's try to understand that as well.

17
00:01:36,700 --> 00:01:39,190
But that as far as the defense is concerned.

18
00:01:39,190 --> 00:01:45,220
So let's compute a pretty good defense that we have answered from the previous patients so that the

19
00:01:45,220 --> 00:01:49,360
place basically replaces the values which are there in the because party in the back.

20
00:01:49,750 --> 00:01:54,490
All of the values apart from those values which are the medical supporting are nullified are either

21
00:01:54,730 --> 00:02:02,740
resorted back to their default values whereas in March the difference has been the values which are

22
00:02:02,740 --> 00:02:08,020
there in the request body only those values are affected at the back end.

23
00:02:08,020 --> 00:02:12,100
But all the values apart from those are unaffected.

24
00:02:12,100 --> 00:02:19,060
So here and we'll try to understand some of these differences more closely and as we'll see some additional

25
00:02:19,060 --> 00:02:25,390
differences if we can uncover the differences between replace and merge both of which I think of update

26
00:02:25,410 --> 00:02:25,930
courts.

27
00:02:25,960 --> 00:02:26,710
So let's proceed.

28
00:02:27,740 --> 00:02:28,470
All right.

29
00:02:28,580 --> 00:02:31,900
So let me just gather my pen please.

30
00:02:32,390 --> 00:02:36,080
So here in first of all we'll create an entity.

31
00:02:36,770 --> 00:02:40,460
So here we are taking an example of the job disk section.

32
00:02:40,490 --> 00:02:43,470
So this is one of the auditing entity which is.

33
00:02:43,480 --> 00:02:45,280
And the success factors application.

34
00:02:45,420 --> 00:02:49,220
So we'll create the data for this particular entity.

35
00:02:49,340 --> 00:02:55,670
There has been primarily that the primary reason of choosing this entity is we wanted to look out for

36
00:02:55,670 --> 00:03:03,290
an entity that has both to create data time and the last updated date time that is both of them exist

37
00:03:03,410 --> 00:03:04,580
in the same format.

38
00:03:04,580 --> 00:03:12,680
That is both our daytime format and our particular object for a particular object for the created daytime

39
00:03:12,890 --> 00:03:15,080
and the last British detection be captured.

40
00:03:15,110 --> 00:03:19,690
So this is one of the entity one of those entities which exist.

41
00:03:19,790 --> 00:03:21,230
So let's proceed with this one.

42
00:03:21,260 --> 00:03:26,690
So first of all we created this particular entity with putting the values for this particular entity.

43
00:03:26,720 --> 00:03:33,440
So let's come back to these light points here and we have created our job description section based

44
00:03:33,440 --> 00:03:40,880
on the existing job description template which mentions as hired for the striker for the Barcelona club.

45
00:03:41,480 --> 00:03:42,720
So we have.

46
00:03:42,720 --> 00:03:47,900
So how does it work out in Texas practices like there is a job description template so based on which

47
00:03:48,220 --> 00:03:51,240
new job descriptions can be created.

48
00:03:51,260 --> 00:03:53,720
Our job description sections could be created.

49
00:03:53,720 --> 00:03:59,960
So there is once a section which has been created out of an existing job description template so the

50
00:04:00,440 --> 00:04:05,240
existing job description template external rule is when there was twenty one.

51
00:04:05,270 --> 00:04:10,250
So this was an already existing entity and we are creating a new section that is the new value that

52
00:04:10,250 --> 00:04:11,420
we are trying to insert.

53
00:04:11,420 --> 00:04:13,990
And basically to create that.

54
00:04:14,000 --> 00:04:16,100
So will fill in the values.

55
00:04:16,100 --> 00:04:21,220
So now on the values which are there for this particular entity.

56
00:04:21,230 --> 00:04:29,600
So all the required values plus the two plus the optional value of the name Ian US and the external

57
00:04:29,600 --> 00:04:31,660
code are being filled in.

58
00:04:31,950 --> 00:04:35,630
So I do understand where they are all the required values for job.

59
00:04:35,630 --> 00:04:40,300
This section let's go to the entity meta data.

60
00:04:40,310 --> 00:04:47,130
So if you go back to a post mental and if you try to execute a call a get call

61
00:04:49,980 --> 00:04:53,440
and we continue to get calls for the entity job section.

62
00:04:53,580 --> 00:04:57,660
So we will gather the entity meta data.

63
00:04:57,840 --> 00:05:05,100
So we'll copy this entity meta data in entirety and basically will place that into digits into every

64
00:05:05,100 --> 00:05:08,960
tool that we understand.

65
00:05:09,510 --> 00:05:17,100
And once we have this and this inquiry tool and in order to find out D in order to find out the required

66
00:05:17,100 --> 00:05:23,130
field what we need to do is we need to query the properties because we are interested in both in navigation

67
00:05:23,160 --> 00:05:25,260
as well as non navigation properties.

68
00:05:25,380 --> 00:05:30,270
So we'll query the genetic part which is properties and we will look out for the properties which are

69
00:05:30,270 --> 00:05:32,040
required is equal to two.

70
00:05:32,160 --> 00:05:35,190
So all the names of those properties which are required.

71
00:05:35,430 --> 00:05:38,610
So here and if you see that these are the.

72
00:05:39,070 --> 00:05:39,350
OK.

73
00:05:39,360 --> 00:05:41,100
So it is showing up 10 20 here.

74
00:05:41,100 --> 00:05:44,880
Line number right forces occupied by an opening square race.

75
00:05:44,880 --> 00:05:49,310
So these are 20 minus one that is 19 fields which are required once.

76
00:05:49,320 --> 00:05:58,260
So if we come back here to the postman to the slight point and here and we see I have all these values

77
00:05:58,290 --> 00:06:02,670
this particular body into the notepad does as possible so let's go there.

78
00:06:02,970 --> 00:06:08,460
So hearing if you see from eleven to thirty one line number.

79
00:06:08,520 --> 00:06:09,930
These are the.

80
00:06:09,930 --> 00:06:10,890
This is the body.

81
00:06:10,890 --> 00:06:13,470
These are in the fields which represent in the body.

82
00:06:13,470 --> 00:06:17,070
So that is seven minus eleven twenty and the one that is twenty one.

83
00:06:17,070 --> 00:06:22,910
So these are the 21 fields and 19 are the required ones two additional that name in us.

84
00:06:22,970 --> 00:06:31,590
There's an optional field which B which will be the description for this particular section in English

85
00:06:32,160 --> 00:06:38,400
and then we have the external code so external calling it is surprising but again there's already bugs

86
00:06:39,420 --> 00:06:45,690
in these things affect those entities that Excel code is a part of a key but still it is not a required

87
00:06:45,780 --> 00:06:46,670
attribute.

88
00:06:47,400 --> 00:06:47,730
All right.

89
00:06:47,970 --> 00:06:58,960
So if you go back here to the to the postman tool we see here that we have the external code but it

90
00:06:59,050 --> 00:07:07,160
is not de acquired because you could do for us it's not required field.

91
00:07:07,310 --> 00:07:07,560
Right.

92
00:07:07,850 --> 00:07:09,340
So that is how it is.

93
00:07:09,430 --> 00:07:13,410
And oh definitely.

94
00:07:15,330 --> 00:07:17,220
Bad press on that.

95
00:07:17,550 --> 00:07:18,720
So yeah.

96
00:07:18,960 --> 00:07:23,960
So now what you do is we try to create the job description template so we'll copy stick with party.

97
00:07:24,330 --> 00:07:34,150
And we go to our postman tool and we'll paste the body and the content type is application slash Jason.

98
00:07:34,410 --> 00:07:37,210
And it's going to be a postcard we live.

99
00:07:37,220 --> 00:07:41,030
Let's put the authorizations in place and we are.

100
00:07:41,040 --> 00:07:48,140
Since we are creating the entity we are not providing any header value of access to GDP matter as much

101
00:07:48,150 --> 00:07:49,650
because that is for an update.

102
00:07:49,650 --> 00:08:02,770
Yet we're creating so will only do offline post and will post the You are all to the entity so we will

103
00:08:02,770 --> 00:08:03,680
be established.

104
00:08:03,700 --> 00:08:04,300
You are right.

105
00:08:04,420 --> 00:08:07,000
And then it's the job description.

106
00:08:07,390 --> 00:08:10,180
That is the entity that is the you are right.

107
00:08:10,210 --> 00:08:14,820
And we want the response back in the JSON format.

108
00:08:14,970 --> 00:08:15,280
All right.

109
00:08:15,670 --> 00:08:23,380
So if you tried to execute this though just to add this to the snowball as the test code is a tree so

110
00:08:23,440 --> 00:08:27,340
Excel called a z test go to the retreat and if you send that

111
00:08:31,900 --> 00:08:32,240
OK.

112
00:08:32,250 --> 00:08:39,900
So we see two hundred one created and the response of the object post operation also returns back the

113
00:08:39,900 --> 00:08:41,280
entity which is being created.

114
00:08:41,280 --> 00:08:44,750
So we get a response party back as well.

115
00:08:44,850 --> 00:08:48,360
So the total site is one point six nine gave you of the response objects.

116
00:08:48,360 --> 00:08:56,870
This includes the body as well as the headers which are being returned from the response object.

117
00:08:56,870 --> 00:08:57,290
All right.

118
00:08:57,510 --> 00:08:59,460
So now we have executed two.

119
00:08:59,550 --> 00:09:01,360
Let's move back to the slide points.

120
00:09:01,660 --> 00:09:04,620
So now we have executed a first call.

121
00:09:04,650 --> 00:09:11,040
So now we have this entity which is already being created just by the understanding so the slide should

122
00:09:11,400 --> 00:09:15,360
the external code as best goes the team but since it was already created now.

123
00:09:15,380 --> 00:09:22,830
So recreate and recreating all the examples with the evaluates Zendesk code 0 0 3.

124
00:09:22,950 --> 00:09:23,280
All right.

125
00:09:23,670 --> 00:09:26,130
So now I'm going back to the next point.

126
00:09:26,130 --> 00:09:33,790
The next stage so here it will be doing a replace goal and where it will be doing the replace call.

127
00:09:33,810 --> 00:09:40,210
It's a much call rather because we are putting the resistance GDP metaphysical too much and then we'll

128
00:09:40,230 --> 00:09:43,450
be posting with the key values providing.

129
00:09:43,740 --> 00:09:48,750
So what we are going to do is like we are let's go through some of these slide points here here in the

130
00:09:48,750 --> 00:09:57,240
issue emerge path to change that description to Becky at the right Barcelona instead of striker at Barcelona.

131
00:09:57,240 --> 00:10:04,990
So this job are the best job description template has been for the Becky not for the striker.

132
00:10:05,010 --> 00:10:07,050
So we changed our description here.

133
00:10:07,230 --> 00:10:13,520
Earlier it was striker so now but this March 1 we want to make it Becky.

134
00:10:14,360 --> 00:10:14,700
All right.

135
00:10:14,700 --> 00:10:17,360
So all of their values are intact now.

136
00:10:18,080 --> 00:10:20,620
So let's say to execute this.

137
00:10:20,670 --> 00:10:22,380
So taking the body

138
00:10:26,890 --> 00:10:27,930
reset on the

139
00:10:33,400 --> 00:10:37,900
list is that here enforcement tool.

140
00:10:38,010 --> 00:10:43,100
We want to do a forced to provide the authorization headers.

141
00:10:43,110 --> 00:10:46,850
We want to do much fun.

142
00:10:51,040 --> 00:11:00,620
We will do a much fun in all caps bodies that we need to have the appropriate you are for that.

143
00:11:00,640 --> 00:11:05,490
So this is going to the right to the job distinction the order the entity along with it.

144
00:11:05,510 --> 00:11:13,410
The key values so the key of the job distinction has been to do so it is like it is both.

145
00:11:13,510 --> 00:11:19,790
If you can see in the entities of the service to this document as well the property reference the keys

146
00:11:19,790 --> 00:11:26,750
are job desktop they don't disconnect from Gordon that is the job description template record of the

147
00:11:26,750 --> 00:11:33,740
job is intended on which the job description section is based and then the external cortex no part of

148
00:11:33,740 --> 00:11:35,270
the job this section.

149
00:11:35,300 --> 00:11:40,910
So this is the actual code is newly created but this value job this temporary already created so we

150
00:11:40,910 --> 00:11:47,590
need to refer the Johnson job this temporary display of call has the already existing value and external

151
00:11:48,080 --> 00:11:52,870
code has a new value that this job this action would be eventually having.

152
00:11:53,210 --> 00:11:58,980
So that has already been created and we had see est going through the routine of the excellent code.

153
00:11:59,120 --> 00:12:04,940
So we need to provide bottom line we need to provide two keys here and how the keys values are being

154
00:12:04,940 --> 00:12:06,250
provided.

155
00:12:06,440 --> 00:12:18,190
If you go to the node plus plus here and then we seek out the values so we can see that on the customer

156
00:12:18,320 --> 00:12:19,890
first.

157
00:12:20,300 --> 00:12:26,620
So we can see here the excellent code is equal to the desired within braces.

158
00:12:26,630 --> 00:12:33,180
We are placing the value of the keys in code as we do the test for it is in a T and then it then fills

159
00:12:33,170 --> 00:12:35,950
in single goods come up job.

160
00:12:35,990 --> 00:12:43,580
This template underscore no code is equal to 1 double 0 2 1 8 1 and then close and think of codes and

161
00:12:43,580 --> 00:12:46,580
the response we are anticipating digits and format.

162
00:12:46,640 --> 00:12:54,530
So once we execute this that I notice that the key it is the value of the job disk section right now.

163
00:12:54,530 --> 00:12:59,510
So if you do a get call in here and then we try to seek out the values.

164
00:12:59,660 --> 00:13:03,710
So this get in the format has been the item format.

165
00:13:04,010 --> 00:13:05,700
So we see that different.

166
00:13:05,750 --> 00:13:13,650
It is for a strike that right now and this strike right now for this post that more to request.

167
00:13:13,730 --> 00:13:17,380
So we are posting that and with our district as 200 okay.

168
00:13:17,900 --> 00:13:25,390
And there is nobody returned that is one party being returned and if we do get call and c cold weather

169
00:13:25,600 --> 00:13:28,440
test for 0 0 2 description has changed.

170
00:13:28,440 --> 00:13:32,280
So we see that description has to do back yet in Barcelona.

171
00:13:32,720 --> 00:13:33,540
So similarly.

172
00:13:33,540 --> 00:13:36,630
So now let's go back to the strike point.

173
00:13:36,650 --> 00:13:44,110
Do not all the required values need to be included for the multiple because we have seen that okay.

174
00:13:44,780 --> 00:13:52,390
Pretty much gone it only mortgages are only whatever but we feel we are sending in the response party

175
00:13:52,400 --> 00:13:54,270
do only would be updated.

176
00:13:54,290 --> 00:14:00,680
And so far the on it has not been a mandated the mandatory requirement to send send in the required

177
00:14:00,680 --> 00:14:01,650
fees.

178
00:14:01,700 --> 00:14:09,110
So but here we have included it for the sake of simplicity so that a comparison between two requests

179
00:14:09,110 --> 00:14:11,390
more than the base could be made easily.

180
00:14:11,870 --> 00:14:14,180
So here it says this Furthermore it's gone.

181
00:14:14,180 --> 00:14:18,570
That is all the data entity is not affected on the selected attributes.

182
00:14:18,650 --> 00:14:25,730
Those are in very carefully for utmost with the new values due to date time should be less than or equal

183
00:14:25,730 --> 00:14:28,680
to the last modified date time.

184
00:14:28,700 --> 00:14:34,640
So here in this particular entity we wanted to have this as we discussed earlier point we wanted to

185
00:14:34,640 --> 00:14:43,570
have both created that time as well as the last modified date time and that too including the time part

186
00:14:43,580 --> 00:14:47,290
so that it could be demonstrated during this life session itself.

187
00:14:47,300 --> 00:14:52,910
So this is one of the entity that came into the picture that the job desk section now here and since

188
00:14:52,910 --> 00:14:59,230
the update has only updated the march marches only to the related attributes.

189
00:14:59,270 --> 00:15:07,040
So herein created because we had created the entity first so it should have been created that created

190
00:15:07,040 --> 00:15:10,220
it should be less than equal to the last modified date thing.

191
00:15:10,760 --> 00:15:12,640
So if you see that now.

192
00:15:12,680 --> 00:15:18,160
So if you try to execute from replacement that get call over the data deliberately and purposely we're

193
00:15:18,170 --> 00:15:29,450
keeping the output format as item because here we can see created the time as the value of the date

194
00:15:29,450 --> 00:15:32,940
and time rather than the job at the time.

195
00:15:33,290 --> 00:15:45,570
So here it will be seeing the value as 10 10 7 weddings the last modified date time has happened to

196
00:15:45,740 --> 00:15:49,930
six fourteen fifty three.

197
00:15:50,370 --> 00:15:58,550
OK so we have two last modified date thing so we'll give you have to compare the exact quarter Max.

198
00:15:58,560 --> 00:16:06,350
So let's say we compared the time of such data types so we take last modified date time and with created

199
00:16:06,360 --> 00:16:14,370
date time for last modified day time has been 10 14 53 and created a daytime is 10 10 0 7 so that created

200
00:16:14,460 --> 00:16:20,580
a time that is 10 10 is less than 10 40.

201
00:16:20,610 --> 00:16:20,940
All right.

202
00:16:21,390 --> 00:16:28,110
So this is where we come to the conclusion that the data is less than to the as modified the time hence

203
00:16:28,140 --> 00:16:34,430
the object was not created from scratch in the call in this particular update.

204
00:16:34,530 --> 00:16:35,760
So let's proceed from there.

205
00:16:36,750 --> 00:16:43,860
And here we have the put operation that is it this operation and if we tried to execute this operation

206
00:16:44,250 --> 00:16:47,650
again we'll put the prescription at the back page.

207
00:16:48,090 --> 00:16:50,190
So let's try to see what happens.

208
00:16:50,190 --> 00:16:59,910
So instead of doing the forced to dip in mortgage we will put up a good call and move ahead from here

209
00:17:00,510 --> 00:17:02,850
and gestural remains the same.

210
00:17:02,850 --> 00:17:04,140
The body remains the same.

211
00:17:04,140 --> 00:17:06,050
The idea is the same.

212
00:17:06,070 --> 00:17:08,540
We make a call and we get 200.

213
00:17:08,550 --> 00:17:11,050
Okay so the response is also the same.

214
00:17:11,250 --> 00:17:14,190
But what happens to the data in time.

215
00:17:14,190 --> 00:17:15,640
Let's see.

216
00:17:16,020 --> 00:17:18,080
We have declared two days time.

217
00:17:18,120 --> 00:17:25,710
So here we have created date time as the intensive seven and the last month if I did them as 10 18 if

218
00:17:25,710 --> 00:17:28,540
we notice that year to date time has remained the same.

219
00:17:28,540 --> 00:17:34,800
So even for that the best goal the understanding on the conceptual level we were trying to build up

220
00:17:34,800 --> 00:17:42,150
is during a baseball an object is created that is an object is destroyed and that a particular key the

221
00:17:42,270 --> 00:17:49,380
object is to recreate it because we need to send all the feeds that are that are required to be there

222
00:17:49,380 --> 00:17:50,770
with the object in the response.

223
00:17:50,790 --> 00:17:52,580
But indeed this party itself.

224
00:17:53,130 --> 00:18:00,900
So better understanding somehow does not hold true so the object is not created but in a virtual understanding

225
00:18:00,930 --> 00:18:06,140
or in a virtual way we can understand it in a way we can only use this for our understanding.

226
00:18:06,160 --> 00:18:12,840
But perspective that vendor of Pascal is made the object is basically all the fields which are there

227
00:18:13,380 --> 00:18:23,590
in the object apart from the ones which are passed in the request body either so either goes back to

228
00:18:23,590 --> 00:18:31,360
the default values or are turned into null values so going to this slide point here the issue at a place

229
00:18:31,360 --> 00:18:36,960
called to change their description to Becky in Barcelona and sort of suckered into Barcelona since it's

230
00:18:36,980 --> 00:18:42,400
their best call and the entity that created all the required values need to be included further.

231
00:18:42,460 --> 00:18:44,270
But a player squad.

232
00:18:44,440 --> 00:18:44,820
All right.

233
00:18:44,980 --> 00:18:46,990
So here this is this mother of baseball.

234
00:18:46,990 --> 00:18:50,460
That is all the data of the entity is affected.

235
00:18:50,470 --> 00:18:57,110
But here also created there is nothing he could do this last if I did that piece the entity is not recreate

236
00:18:57,160 --> 00:19:00,420
it but only all the data is modified somehow.

237
00:19:00,430 --> 00:19:01,330
Which others.

238
00:19:01,360 --> 00:19:08,920
Well it is also a type of a big request and regulation of energy would not have qualified it as an update

239
00:19:09,220 --> 00:19:12,910
a.

240
00:19:12,950 --> 00:19:18,530
So then how have you understood the concept or let's proceed further.

241
00:19:19,070 --> 00:19:24,960
So here it will see the difference between the request and much so let's see.

242
00:19:25,060 --> 00:19:27,380
So we what we do is link them the first use gives.

243
00:19:27,380 --> 00:19:33,020
We are using a post called access to a different method is called to most of that is a march call and

244
00:19:33,020 --> 00:19:40,130
will execute the merge call wherein we will place these particular object and a team.

245
00:19:40,130 --> 00:19:47,130
What happens so let's go back to not just those millions have copied this this particular object.

246
00:19:47,210 --> 00:19:52,250
So let's use this party and

247
00:19:54,860 --> 00:20:03,530
this party and we have the you are I provided the keys for the job.

248
00:20:03,540 --> 00:20:04,320
This section.

249
00:20:04,340 --> 00:20:04,600
OK.

250
00:20:04,620 --> 00:20:09,230
So it was the same should not have changed.

251
00:20:09,240 --> 00:20:10,560
What are you relative in the same.

252
00:20:10,890 --> 00:20:15,570
But here we are placing these key values and everything else remains.

253
00:20:16,450 --> 00:20:16,740
OK.

254
00:20:16,740 --> 00:20:21,150
So it's supposed well right post that it's too much fun.

255
00:20:21,660 --> 00:20:26,820
So we have to put X etched deeply a dash.

256
00:20:27,490 --> 00:20:31,320
And its value as marginal and they're all in cash.

257
00:20:31,410 --> 00:20:36,990
And if we try to a C Q now which isn't much fun.

258
00:20:37,230 --> 00:20:45,630
So what we get Okay so we are getting an error for the top five without a low header.

259
00:20:46,200 --> 00:20:53,460
So we have to have the authorization benefits we have the header X GDP matured.

260
00:20:53,550 --> 00:20:59,080
Now we had access to whether it's a header by try to execute it.

261
00:20:59,100 --> 00:21:02,160
Now all right so we get to it.

262
00:21:02,170 --> 00:21:02,610
OK.

263
00:21:03,070 --> 00:21:05,720
And so just executed fine right.

264
00:21:05,740 --> 00:21:12,340
It does not get any error philosophy to please this particular header and you can make a place call

265
00:21:12,340 --> 00:21:18,060
allow with the same body that we have for the merger request

266
00:21:20,820 --> 00:21:21,310
right.

267
00:21:21,470 --> 00:21:22,030
So.

268
00:21:22,450 --> 00:21:26,320
Let's complete the first use case here in the issue of multiple.

269
00:21:26,590 --> 00:21:31,860
But with only the selected foods we modified and also not including all the required fees.

270
00:21:32,110 --> 00:21:34,140
If you notice are not all the required fees.

271
00:21:34,150 --> 00:21:40,820
So there are 19 declared foods but we have only included three which are not all the required foods.

272
00:21:40,830 --> 00:21:48,810
So and we have made a I'm I made a mighty request and it showed us these trade offs to adhere to.

273
00:21:48,840 --> 00:21:49,390
OK.

274
00:21:49,500 --> 00:21:55,800
So now with the same use case if you have used a book on that you get a place called Let's see where

275
00:21:55,810 --> 00:21:57,500
we have that have happen.

276
00:21:57,660 --> 00:22:01,040
So how are these authorizations are in place in the body.

277
00:22:01,050 --> 00:22:02,540
Same body same.

278
00:22:02,580 --> 00:22:05,580
You are also we have the so-called equals 2.

279
00:22:05,580 --> 00:22:12,720
So we notice that there are more than one key keys for a particular object then we need to place the

280
00:22:12,720 --> 00:22:21,690
key values as the key name equals to the key value here equals to the important business not colon which

281
00:22:21,700 --> 00:22:24,370
is normally in the auditor or D.

282
00:22:24,390 --> 00:22:32,500
So here in the U.S. right is key equals good value and commerce have keys values to pass.

283
00:22:32,550 --> 00:22:33,960
And if you type execute it.

284
00:22:35,640 --> 00:22:37,720
So here in D.C. magic.

285
00:22:37,830 --> 00:22:42,120
So these add required properties and payload required properties.

286
00:22:42,130 --> 00:22:43,660
So and these are.

287
00:22:43,740 --> 00:22:48,030
And it lists all the required properties depending upon department object.

288
00:22:48,030 --> 00:22:59,200
So as we discussed upon earlier the maturity of an application is very closely felt by the by the eye

289
00:22:59,450 --> 00:23:02,010
color error messages that sense.

290
00:23:02,010 --> 00:23:04,380
So this is one such application.

291
00:23:04,380 --> 00:23:04,770
All right.

292
00:23:05,160 --> 00:23:09,340
So so let's go through the state points.

293
00:23:09,360 --> 00:23:14,520
So here in the issue of replaced Colbert you don't need this latitude to modify it and also not including

294
00:23:14,520 --> 00:23:16,120
all the required fees.

295
00:23:16,230 --> 00:23:20,620
So we get the status for our back request all right.

296
00:23:21,040 --> 00:23:23,590
So we get these adequate food did not fail.

297
00:23:23,710 --> 00:23:30,130
So this helps us understand that another striking difference is there between the replace and the much

298
00:23:30,230 --> 00:23:40,180
call is that the replace call requires all the required fees at least to be placed in the request body

299
00:23:40,510 --> 00:23:49,260
because the objective of the replace call is to replace all the values which are dead in the replace

300
00:23:49,290 --> 00:23:55,930
all the values of DB back in the values of the request that is coming in.

301
00:23:55,930 --> 00:24:04,420
So if the quantity of food is here so this goes right like the rest of the fields would be either returned

302
00:24:04,420 --> 00:24:10,990
back to the no value or they would be returned back to their default values but here in a sense we are

303
00:24:10,990 --> 00:24:13,540
not providing the value of the required fees.

304
00:24:13,630 --> 00:24:20,030
So you need to understand application need to understand what are the required values need to be so

305
00:24:20,030 --> 00:24:27,310
deep that many in the help desk on my table can go in without adequate fees.

306
00:24:28,670 --> 00:24:29,270
So I'm right.

307
00:24:29,300 --> 00:24:36,270
So this has been to some striking differences between the two place and the update got hope decision

308
00:24:36,320 --> 00:24:38,610
has been an interesting one.

309
00:24:38,990 --> 00:24:40,710
Thank you for your listing.

310
00:24:40,730 --> 00:24:42,340
Stay tuned and happy.