1
00:00:00,410 --> 00:00:01,030
Hi.

2
00:00:01,080 --> 00:00:04,530
So welcome to yet another session on success factors.

3
00:00:04,530 --> 00:00:13,430
And here we'll be taking this discussion further over the rules that to to be I've got to expand barometer

4
00:00:13,870 --> 00:00:16,760
when navigated from one entity to the amateur.

5
00:00:17,610 --> 00:00:25,330
So here and we'll discussing all the scenario where we have the ENP employment and if come as a cutting

6
00:00:25,780 --> 00:00:26,270
so here.

7
00:00:26,300 --> 00:00:34,040
Ian Lee employment is the base entity and company recurring is the navigation entity that is the target

8
00:00:34,040 --> 00:00:36,430
entity of the child entity.

9
00:00:36,910 --> 00:00:39,800
So the committee that we will be executing over here this.

10
00:00:39,810 --> 00:00:43,920
So this is to order W2 is an auditor you are right.

11
00:00:43,920 --> 00:00:50,740
Then we add the ENP employment object logistic base and Tea Party favorite object and from there.

12
00:00:50,820 --> 00:00:57,960
And on top of it we are different that applied either equal to one set of T double to six and then we

13
00:00:57,960 --> 00:01:02,690
are making an expand to the com in for a navy.

14
00:01:03,030 --> 00:01:09,930
And to that end Navy we didn't come in for a navy which is the MPP com recurring and Navy.

15
00:01:10,110 --> 00:01:12,650
So it just sort of nested navigation.

16
00:01:12,950 --> 00:01:20,320
So from the parent which is the ENP alignment we will go into the company for a navy.

17
00:01:20,370 --> 00:01:26,490
So comping for a Navy as we have seen earlier this corresponds to the ENP compensation.

18
00:01:27,270 --> 00:01:35,470
And from that DMP compensation check they'll be navigating to the MPP contradictory object piety and

19
00:01:35,560 --> 00:01:43,440
typical rhetoric and Navy point to note over here is the base MP employment object is a non effective

20
00:01:43,440 --> 00:01:44,720
dated entity.

21
00:01:44,970 --> 00:01:52,290
Where is the end navigation near complicating is an effective data thus and typically that is an advanced

22
00:01:52,290 --> 00:01:57,150
effective dated entity if you tried to visualize this navigation.

23
00:01:57,150 --> 00:02:06,050
So how is it happening is that we're on here on the end and by McArthur we will navigate via these companies

24
00:02:06,080 --> 00:02:08,110
for Navy on.

25
00:02:08,340 --> 00:02:14,060
So here in the company finally by the company for a navy we will navigate through into the MP compensation

26
00:02:14,740 --> 00:02:22,550
and from MP compensation the entity that we have available over here is a big big company carrying a

27
00:02:22,550 --> 00:02:28,460
navy and via that we'll be navigating into the ambit become recurring.

28
00:02:28,510 --> 00:02:34,340
So in the sense how the navigation is happening over here is from the MP employment will come to the

29
00:02:34,340 --> 00:02:43,300
MP compensation or take from the MP compensation object will go up to the MP become a recurring object

30
00:02:43,900 --> 00:02:45,810
like all right.

31
00:02:46,120 --> 00:02:55,180
So now let's understand this behaviour vino MP employment is a non effective dated entity and the compensation

32
00:02:55,240 --> 00:02:59,230
is an effective dated entity it has got only the start date.

33
00:02:59,360 --> 00:03:05,410
There is a sequence number and the MP complicating is an advanced effective dated entity.

34
00:03:05,410 --> 00:03:09,510
It is a policy question but along with the starting line.

35
00:03:09,900 --> 00:03:18,470
So this is how we are navigating into this particular discussion to coming to decide points here.

36
00:03:19,210 --> 00:03:20,740
What we will do it now is.

37
00:03:20,740 --> 00:03:22,810
So we will execute this query.

38
00:03:22,810 --> 00:03:28,980
We notice that there is no from date to date and as of the overhead in this particular query and since

39
00:03:28,990 --> 00:03:31,510
ENP employment is a non effective dated entity.

40
00:03:31,990 --> 00:03:36,720
So now let's see how that propagate so let's try to execute this query.

41
00:03:36,740 --> 00:03:47,860
So we'll go into the notepad best plus so I've already got this particular query you've got here.

42
00:03:48,140 --> 00:03:58,820
So let me copy this and let's go to the post trend to let's take a new tab is really what you think

43
00:03:58,900 --> 00:04:00,350
authorisations.

44
00:04:00,440 --> 00:04:05,240
They say that transitions like you did.

45
00:04:05,440 --> 00:04:07,170
So what we would get to watch here is.

46
00:04:07,190 --> 00:04:14,150
So first of all we have called the parent record that is corresponding to the the record idea or the

47
00:04:14,150 --> 00:04:17,310
unique instance of the ESPN climate object.

48
00:04:17,320 --> 00:04:17,820
Yes.

49
00:04:17,960 --> 00:04:24,580
Let's go to the space and copy the parent entity first.

50
00:04:24,970 --> 00:04:32,250
We have caught one record here for the parent.

51
00:04:32,390 --> 00:04:33,400
So this is an array.

52
00:04:33,410 --> 00:04:34,650
So we have caught.

53
00:04:34,670 --> 00:04:35,000
Yes.

54
00:04:35,000 --> 00:04:36,840
Only one record for the parent.

55
00:04:36,890 --> 00:04:42,050
Now we will navigate to the ENP compensation object via the company for a navy.

56
00:04:42,140 --> 00:04:47,650
So we will get the com in for any expanded as well.

57
00:04:47,650 --> 00:04:50,830
So here we have common interests.

58
00:04:50,880 --> 00:05:01,030
So yes again comping for MTV really take the unique idea of the parent off of the child of the parent

59
00:05:01,030 --> 00:05:09,900
entity here which opportunity comp and fine navy so definitely take child fun and it is the comp and

60
00:05:09,900 --> 00:05:16,800
for a Navy and now we've been have the grand trained

61
00:05:20,820 --> 00:05:21,340
right.

62
00:05:21,440 --> 00:05:28,430
So from within the company for a navy we will navigate through the MPP company getting a navy and ready.

63
00:05:28,490 --> 00:05:29,270
This is T.

64
00:05:29,680 --> 00:05:36,030
And let's see how many deserves to be able to here sensitive and ready area the airport.

65
00:05:36,050 --> 00:05:37,990
One reason we're here.

66
00:05:38,120 --> 00:05:40,820
At that point in time for this listing

67
00:05:44,140 --> 00:05:49,640
value for a competent settled.

68
00:05:49,770 --> 00:05:50,180
All right.

69
00:05:51,440 --> 00:05:56,900
So at that point in time the woman would not have been any other competent available otherwise you would

70
00:05:56,900 --> 00:06:00,480
have also been come in or another company would have to be come in.

71
00:06:00,600 --> 00:06:07,610
But this is what devalue of decline child is like so nobody would have to infer is the value of the

72
00:06:07,610 --> 00:06:14,940
grandchild given that we have we have been given the original query which is this.

73
00:06:15,150 --> 00:06:23,180
Now conceptually we have to arrive at Port call should we be made to the grandchild so that we get the

74
00:06:23,480 --> 00:06:24,420
same result.

75
00:06:24,560 --> 00:06:31,310
Now what we would be doing is we would be applying the rules that we have been learning on a conceptual

76
00:06:31,310 --> 00:06:38,600
level and then try to execute the query the endpoint query that we make on the grandchild and we will

77
00:06:38,600 --> 00:06:46,200
execute that by the post to our right and then we will see whether it returns the same unique card.

78
00:06:46,290 --> 00:06:46,680
All right.

79
00:06:46,930 --> 00:06:48,610
So let's first of all.

80
00:06:48,620 --> 00:06:50,620
So what we will do is go step by step.

81
00:06:51,130 --> 00:06:56,680
So the first is like we have to navigate from the parent entity to the child entity.

82
00:06:56,710 --> 00:07:02,410
Now since we know that the parent entity is a non effective dating entity.

83
00:07:02,410 --> 00:07:10,630
So how we will be reducing the child entity they will apply one of the rules which is applicable from

84
00:07:10,630 --> 00:07:17,500
the 49 effective data to the effective data navigation which is if the base entity is not effective

85
00:07:17,500 --> 00:07:23,430
dated but it is used as adopted when expanding the navigation entity.

86
00:07:23,430 --> 00:07:30,700
So we'll come here and do the node by bus pass and we reduce the query for EMV compensation which is

87
00:07:30,700 --> 00:07:31,580
the child.

88
00:07:31,740 --> 00:07:41,860
So will apply here is for child let's say the right section and here and we have for that child fine

89
00:07:42,180 --> 00:07:45,830
which is here we have the employee compensation.

90
00:07:46,110 --> 00:07:56,960
And we will put in the filter to get first of all and put up for we come to Tucson and dollar equals

91
00:07:57,720 --> 00:08:01,180
we will put in the use that I d.

92
00:08:02,040 --> 00:08:08,390
He calls one day to be able to fix all right.

93
00:08:08,880 --> 00:08:15,980
And what we will put up is since we are navigating from the non effective data to be activated object

94
00:08:15,980 --> 00:08:21,480
we give the employee compensation the heads up that he has of data needs to be applied which would be

95
00:08:21,480 --> 00:08:29,470
the current to date so we have this value and we will try.

96
00:08:29,830 --> 00:08:36,240
So now this is for the child right now given that this it becomes the parent of the grandchild right.

97
00:08:36,270 --> 00:08:44,050
So this the parent of this up of the grandchild now given this query what we will derive D grandchild

98
00:08:44,050 --> 00:08:57,500
now grandchild would come out as we have haven't declared J The and b become a recurring check to it

99
00:08:57,840 --> 00:09:05,710
is to become a recurring as a grandchild and what we will put up this question mark.

100
00:09:05,820 --> 00:09:24,780
Dollar for Mark for Mark DeCosta Jesus son and we will have dollar fell to equals user Ida equal 1 0

101
00:09:24,780 --> 00:09:25,950
3 to the 6

102
00:09:29,360 --> 00:09:31,600
and herein.

103
00:09:31,670 --> 00:09:35,690
The thing is since now we will take this as a parent.

104
00:09:35,690 --> 00:09:39,340
So here we have applied the adopted parameter on the parent.

105
00:09:39,800 --> 00:09:47,840
And if we navigate from an effective dated entity to another effective dated entity what we do normally

106
00:09:47,840 --> 00:09:53,970
is effective started become state has opted for the child entity.

107
00:09:54,230 --> 00:09:57,410
But herein we have also already applied to adopt it.

108
00:09:57,410 --> 00:10:03,950
So what happens is there is a rule which says let's go back to this slide rule which says a fund specified

109
00:10:04,010 --> 00:10:06,150
as Update Desk query option.

110
00:10:06,200 --> 00:10:11,270
All entities in all levels of the query use the status as off date.

111
00:10:11,330 --> 00:10:22,520
So we have since we have the update and the parent 30 percolate down Rudy child here and will face up

112
00:10:22,770 --> 00:10:28,760
to as of late because the same value which we have.

113
00:10:29,440 --> 00:10:31,890
So it is for a lot of over here.

114
00:10:32,060 --> 00:10:41,100
Now if try to execute this independent really in the placement tool let's try to execute this here.

115
00:10:43,890 --> 00:10:45,980
And we have the authorization has been through a lot

116
00:10:50,040 --> 00:10:51,010
executed.

117
00:10:51,040 --> 00:10:53,000
So do the results that comes up.

118
00:10:53,330 --> 00:10:57,100
And how many is the shooter on Dupont decorated which is dead.

119
00:10:57,500 --> 00:11:03,500
And this is a unique instance of the record that is being written along with the key value if we go

120
00:11:03,490 --> 00:11:08,510
into the notes that blessed us and we see that again that derived deserves to be God.

121
00:11:08,540 --> 00:11:12,050
40 grand child is

122
00:11:15,090 --> 00:11:16,250
this particular value.

123
00:11:17,040 --> 00:11:22,020
And now if you see big companies base salaries so we just pull up over here.

124
00:11:22,020 --> 00:11:29,630
The sequences for all that is equal to for all and the start date is what's generated the 19 start it

125
00:11:29,640 --> 00:11:34,070
is first generated then 19 and then you residency double to 6.

126
00:11:34,370 --> 00:11:40,920
Which is exactly the same which has been turned back from the original query and which the system has

127
00:11:40,920 --> 00:11:47,610
followed the same as the bottom of the rules and return but here to be manually followed all the entire

128
00:11:47,610 --> 00:11:51,350
rules and we basically were able to deduce the same result.

129
00:11:51,810 --> 00:12:00,090
So this firm up our understanding mode and understanding that help expand behavior is undertaking between

130
00:12:00,250 --> 00:12:03,050
the navigation happens between two entities.

131
00:12:04,940 --> 00:12:06,770
To come into the slide points.

132
00:12:06,890 --> 00:12:11,540
So what are rules did we apply over here so we applied for Rule number two.

133
00:12:11,580 --> 00:12:18,120
And rule number four and we variable could reduce and however we can also dig into point the effectively

134
00:12:18,120 --> 00:12:24,560
to the entity rule like if the navigation entities MCP These enable then as of data deaths record having

135
00:12:24,560 --> 00:12:26,270
the highest sequence number.

136
00:12:26,320 --> 00:12:32,660
If we saw here because it returns to record having the highest that's somebody that is for that level

137
00:12:33,080 --> 00:12:35,470
so otherwise it would have returned by 2 3 and 4.

138
00:12:35,480 --> 00:12:39,420
If people have use from disputed regions all right.

139
00:12:39,440 --> 00:12:47,000
So these are the three rules that applied in order to deduce how what would be the end result coming

140
00:12:47,000 --> 00:12:54,170
up are what would be the behavior of X fan when navigating between these non effective data the entity

141
00:12:54,770 --> 00:13:02,360
to and other effective digital entity and has fought to effectively thus end CPD any entity.

142
00:13:02,670 --> 00:13:05,630
So now let's try to take up another scenario.

143
00:13:08,030 --> 00:13:09,030
Now here.

144
00:13:09,500 --> 00:13:15,980
So this is another scenario built in Vietnam navigating from the currency exchange rate to currency

145
00:13:16,400 --> 00:13:23,600
now the base is an effective dated entity and that the navigation which is currency is also an effective

146
00:13:23,650 --> 00:13:24,980
dated entity.

147
00:13:25,340 --> 00:13:31,740
So what we are executing over here is we are executing a query over currency exchange rate the farmer

148
00:13:31,760 --> 00:13:40,490
data could produce and as of very difficult to first of all first of all tuber 2013 and we are placing

149
00:13:40,490 --> 00:13:48,440
the food that we source currency equals USD and Target's currency equals zero and we will order by effective

150
00:13:48,670 --> 00:13:50,860
start date descending.

151
00:13:51,110 --> 00:13:56,870
And then we will navigate through these sorts currency and Navy and which basically determines which

152
00:13:57,290 --> 00:13:59,450
currency object right.

153
00:13:59,810 --> 00:14:05,980
So first of all before we execute this query so let's seek out a bit of an understanding of what where

154
00:14:05,990 --> 00:14:10,310
does the currency exchange rate object holds.

155
00:14:10,310 --> 00:14:19,870
So if you go here and we go into the site and will try to query this make this query happen on comment

156
00:14:19,910 --> 00:14:20,830
on the front.

157
00:14:20,840 --> 00:14:27,700
This query query on the currency exchange rate object within the format outputs.

158
00:14:27,820 --> 00:14:32,480
Jason from where we really are facing us 1st of January 2013.

159
00:14:32,630 --> 00:14:40,910
That is the effective and the date is basically greater than equal to the 1st of January 2000 13 and

160
00:14:40,910 --> 00:14:44,860
what we are saying is salt could assist us to in targeted currencies Europe.

161
00:14:44,930 --> 00:14:51,650
So that means we are seeking out the information of the exchange rate where across a period of across

162
00:14:51,650 --> 00:14:53,500
the times after.

163
00:14:53,600 --> 00:14:59,630
So during 2013 and went into source currencies you will see and be targeted given this is Europe that

164
00:14:59,630 --> 00:15:03,020
is USD to euro conversion rate.

165
00:15:03,050 --> 00:15:09,350
So if we tried to execute it and it is ordered by effective started ascending.

166
00:15:09,500 --> 00:15:14,420
Let me put in the authorizations this all right.

167
00:15:14,470 --> 00:15:15,940
So here we get that.

168
00:15:15,940 --> 00:15:16,400
Okay.

169
00:15:16,840 --> 00:15:23,590
When it was nineteen hundred one then the effective start date was due to first of January 2000.

170
00:15:23,630 --> 00:15:35,700
So in nineteen hundred so in the exchange rate was point 8 9 2 0 9 for USD to euro convergence.

171
00:15:35,700 --> 00:15:41,940
So this used to you can source currency issue with T and the target currency is euro.

172
00:15:41,940 --> 00:15:47,700
So one US dollar amount to 2.8 9 2 0 9 euros.

173
00:15:48,210 --> 00:16:00,560
So it was in the from 0 1 2 1 nineteen hundred four had support and it indeed on the 1st of June 2016

174
00:16:01,170 --> 00:16:06,190
the value of the exchange rate and it's been point Tripoli to 1 right.

175
00:16:06,650 --> 00:16:11,190
So this is how it sure did it was on the 22nd of June.

176
00:16:11,240 --> 00:16:13,940
It has been point 8 8 6 1.

177
00:16:14,120 --> 00:16:24,320
And similarly on the Tour de toll of fuel it has been pointing at 7 9 5 between enthusing for some time

178
00:16:25,220 --> 00:16:29,940
and then if you see on the 24th of June at this point eight nine nine.

179
00:16:30,020 --> 00:16:30,660
Right.

180
00:16:30,680 --> 00:16:40,350
And then when you see on the 7th of June it is 9 0 7 5 meaning enthusing and then we see on target September

181
00:16:40,360 --> 00:16:42,240
two thousand six.

182
00:16:42,470 --> 00:16:45,400
Dean it is point 8 9 2.

183
00:16:45,680 --> 00:16:47,720
So this is how the information is being played.

184
00:16:47,720 --> 00:16:55,340
So currency exchange rate object is supposed to give these exchange rate information for currency cross

185
00:16:55,340 --> 00:16:59,490
currency conversions across to different date.

186
00:16:59,900 --> 00:17:05,390
So this is a perspective that is the objective of this particular currency to balance the exchange your

187
00:17:05,560 --> 00:17:06,070
check.

188
00:17:06,440 --> 00:17:13,560
So herein but we're trying to do here it's so let's try to first of all execute this query and we know

189
00:17:13,830 --> 00:17:19,240
both because if the exchange rate and the currency are the effective dated objects.

190
00:17:19,350 --> 00:17:19,600
Right.

191
00:17:19,860 --> 00:17:20,990
So let's go.

192
00:17:22,020 --> 00:17:23,640
Couple of points here.

193
00:17:23,640 --> 00:17:30,450
These nor did I do navigation is present from currency exchange rate to currency by name so currency

194
00:17:30,450 --> 00:17:36,450
and we entered the currency entity as illustrated in the service matters in the document also can be

195
00:17:36,450 --> 00:17:42,300
in French from digital and Martin navigator given here is an example of the currency exchange rate information

196
00:17:42,620 --> 00:17:45,300
for conversion from us to to Europe.

197
00:17:45,300 --> 00:17:45,540
Right.

198
00:17:45,900 --> 00:17:54,120
So if you come here I've just pasted this screenshot from the order to model navigator so we can see

199
00:17:54,120 --> 00:18:01,370
that there is one source currency navigation and one target currency navigation which is available when

200
00:18:01,380 --> 00:18:05,760
we navigate from deep sea exchange rate to currency.

201
00:18:05,760 --> 00:18:11,930
So this is the source telling CNN We understand its currency and even navigation right.

202
00:18:11,940 --> 00:18:15,390
So we are making use of this source currency navigation within.

203
00:18:15,400 --> 00:18:18,630
So we want to know the details about this false currency.

204
00:18:19,620 --> 00:18:22,190
So now let's try to execute this particular query.

205
00:18:22,260 --> 00:18:29,260
So let's go through the notes breathlessness and here and we will take the query this one and we'll

206
00:18:29,280 --> 00:18:36,780
try to go and put it up in the postman tool and try to get those details.

207
00:18:36,840 --> 00:18:46,040
So here you have to have put OK so here that isn't as an array.

208
00:18:46,150 --> 00:18:51,430
And there's only one record which you've been shown up and this is the record you didn't record.

209
00:18:51,530 --> 00:19:02,240
So let's capture that parent is this hand that can actually be child which could be let's go to the

210
00:19:02,240 --> 00:19:06,120
source currency and Navy and get towards currency envy.

211
00:19:06,130 --> 00:19:12,500
And it is it is not and it is only one record which is going to be out with it.

212
00:19:12,600 --> 00:19:18,070
So another was captured which I regard and here in the south.

213
00:19:18,140 --> 00:19:18,520
What.

214
00:19:19,000 --> 00:19:25,390
So now what we are going to do is conceptually we will seek out what should be detailed given this query

215
00:19:25,390 --> 00:19:35,210
executed so we know that again time is the currency object and we need to basically provide in certain

216
00:19:36,030 --> 00:19:45,930
of course I will put up before my physical Jason and the dollar folder is equal to the put different

217
00:19:46,210 --> 00:19:57,970
as the code is equal to USD for gold equals you which is the source currency and what we need to put

218
00:19:57,970 --> 00:20:01,180
up here whether it should be from there to it or adopted.

219
00:20:01,540 --> 00:20:11,230
Now we see in the query that we have the parent query that we have there is no also there is a specific

220
00:20:11,230 --> 00:20:15,900
causal isn't adopted which is being applied which is 2013

221
00:20:17,970 --> 00:20:23,280
2013 and October 1st of October 2013 has been applied over here.

222
00:20:23,530 --> 00:20:29,610
So now we know that if an update is applied then it is propagated at all levels.

223
00:20:29,640 --> 00:20:33,180
So to both objects are active effective it as well.

224
00:20:33,180 --> 00:20:39,960
So we put the as of date is equal to what we have to mind the case.

225
00:20:40,080 --> 00:20:51,030
So that update has to be the same two thousand 13 2 0 1 3 Very very very very m of Trooper the 2 to

226
00:20:51,030 --> 00:20:51,300
1.

227
00:20:51,630 --> 00:21:02,460
So not if we executed this particular call then it could give us the exact same instance of deep child

228
00:21:02,790 --> 00:21:03,960
up check.

229
00:21:03,960 --> 00:21:04,510
Right.

230
00:21:04,560 --> 00:21:13,020
So let's execute this particular call over deportment tool and here we execute this call.

231
00:21:13,070 --> 00:21:19,410
We have the authorizations and basic authorizations and if you tried to execute this particular call

232
00:21:19,870 --> 00:21:23,610
and here we see the results area so we have an output.

233
00:21:23,950 --> 00:21:35,830
And here in DC Cody unique they Heidi highly instance of the currency object and here we get the output

234
00:21:36,190 --> 00:21:42,630
of that particular thing of the unique the unique card are a unique instance of currency so this code

235
00:21:42,700 --> 00:21:51,030
is equal to USD we can vary in quality steep and effective to this one 1 1990 2 1 1 1980.

236
00:21:51,120 --> 00:21:58,100
So it is the same as that of the child it has been gathered by our innovation.

237
00:21:58,240 --> 00:22:03,940
So we are in line with these rules and we are following them and we are able to conceptually validate

238
00:22:03,940 --> 00:22:04,940
that as well.

239
00:22:05,530 --> 00:22:07,080
So coming to this point.

240
00:22:07,180 --> 00:22:13,420
So the rule applied here has been if you specified as update as the query option all entities in all

241
00:22:13,420 --> 00:22:15,730
levels of the query uses this data.

242
00:22:16,000 --> 00:22:17,840
As of late.

243
00:22:18,070 --> 00:22:25,720
So proceeding to the next slide here in the event at the example involving the same objects which we

244
00:22:25,720 --> 00:22:31,260
have the exchange rate and currency but hearing in the query that we have.

245
00:22:31,340 --> 00:22:37,050
We have executed over the currency exchange rate we have the same death rate in so its currency value

246
00:22:37,080 --> 00:22:43,960
is due to the currency at zero and we have ordered by effective started sending and we are expanding

247
00:22:43,960 --> 00:22:52,980
this source currency NIV but here we have not applied any as of 8 are from our good barometer.

248
00:22:53,410 --> 00:22:54,460
So what would happen.

249
00:22:54,470 --> 00:22:59,320
So let's try to first of all execute this query and see complete results.

250
00:22:59,350 --> 00:23:00,890
So let's go to the notepad.

251
00:23:01,020 --> 00:23:03,970
Plus I have already copied this query over here.

252
00:23:04,450 --> 00:23:08,330
And if we tried to execute that in deportment tool.

253
00:23:08,830 --> 00:23:15,840
So we put up the query and then we'll provide the authorizations and send it across.

254
00:23:16,120 --> 00:23:25,390
And what we get is so certain survey and we have heard only one output and died out our test for the

255
00:23:25,390 --> 00:23:27,330
parent here.

256
00:23:27,570 --> 00:23:36,310
Let's record this and then for the child which is the to see so its currency and Navy and the GC currency

257
00:23:36,310 --> 00:23:37,670
of check.

258
00:23:37,730 --> 00:23:46,030
So we basically take up this particular unique consensus of the currency object that we have now given

259
00:23:46,030 --> 00:23:53,050
that we have this source query and since we have to now derive the value of the change in an independent

260
00:23:53,050 --> 00:23:53,580
credit.

261
00:23:53,920 --> 00:23:56,710
So what we would do is we derive it now.

262
00:23:56,770 --> 00:24:05,950
So we have to navigate to the currency object and we have format to close to the sun and we have dollar

263
00:24:06,340 --> 00:24:13,890
coins the equals the code he calls you with D.

264
00:24:14,020 --> 00:24:15,060
Is that the case.

265
00:24:15,100 --> 00:24:15,690
Yes.

266
00:24:15,710 --> 00:24:20,100
Or it puts you in c because we are doing for the source currency which is as follows.

267
00:24:20,350 --> 00:24:24,090
And what we need to specify over here now.

268
00:24:25,360 --> 00:24:30,660
So now there is a rule which says it okay for an effective day to day to the or if there is no filter

269
00:24:30,670 --> 00:24:38,080
which is that if there is no from day to day or adopted been applied then implicitly there is is a that

270
00:24:38,090 --> 00:24:42,400
is equal to today's date which is implied just applied.

271
00:24:42,430 --> 00:24:50,620
So if you seek out briefly here so which since the rule number seven is no date either from birth to

272
00:24:50,650 --> 00:24:57,870
the date is a specified in the query the system applies the filter as I did with today's got introduced

273
00:24:57,900 --> 00:25:01,130
as a value of t as of date.

274
00:25:01,150 --> 00:25:02,980
So this is implicitly applied.

275
00:25:03,100 --> 00:25:06,510
So when we executed the period we are the traditional queries.

276
00:25:06,580 --> 00:25:13,570
I think that as a very difficult to the dash zero one dash 13 corrected data which was already applied

277
00:25:14,080 --> 00:25:17,430
and then this end of rule that followed this label.

278
00:25:17,680 --> 00:25:23,280
If an update is applied at one level so it is virtually quality to all these levels.

279
00:25:23,290 --> 00:25:31,720
So taking these two views into account we would come down and say that okay as of date has to be applied

280
00:25:31,800 --> 00:25:40,460
and it is deep current that we need to apply over here.

281
00:25:40,630 --> 00:25:51,820
So then if we try to execute this query and if we go to the postman to try to execute this query and

282
00:25:51,820 --> 00:25:55,110
we seek out they are reserved.

283
00:25:55,120 --> 00:26:03,310
And since it is an array and we are getting one output so we can say and check out whether this is the

284
00:26:03,310 --> 00:26:08,940
unique recording since that report earlier earlier what record is called a US D.

285
00:26:08,980 --> 00:26:09,430
Yes.

286
00:26:09,550 --> 00:26:13,220
And the fact you started this 1990 0 1 0 1.

287
00:26:13,210 --> 00:26:18,470
So that is in line with what we have gathered from executing the original query.

288
00:26:18,490 --> 00:26:26,140
So the understanding that the building is in alignment with these rules does have been stated 40 dollar

289
00:26:26,210 --> 00:26:33,790
expand the area and we have been able to understand that concept and we are able to predict the value

290
00:26:33,790 --> 00:26:36,960
of the child that should be exhibited.

291
00:26:38,290 --> 00:26:42,730
So I hope this other informative session and that useful to you.

292
00:26:42,730 --> 00:26:44,070
Thanks for listening.

293
00:26:44,080 --> 00:26:45,760
Stay tuned and happy learning.