Let's understand what does the external look of relationship so in the previous lecture we talked about
the gender look up relationship the indirect look up relationship and also when we use that kind of
relationship.
So now let's talk more about the extent I look a relationship so as to already be understood the differentiation.
Let me just do a quick recap.
So when the child object is an external object and the phantom object is a sales full standard or a
custom object the goal for either the gender lookup or the indirect lookup relationship.
So if we go for the general look of relationship in case the child external object stores the 18 digit
sales pulls out a card 18 that by four does not.
And if it is connected through a different commonality then we go for the indirect relationship.
That is why the matching feel in the parent does this fanciful Is that a card idea here that has the
matching feel here is some other custom unique external 80 food.
In our case that was the customer idea food that was a unique external feeling going to object that
we used to establish that relationship.
Perfect.
So all that aside now coming to the external look up relationship we create external look a relationship
when the child object is an external object and the parent is also an external object.
So in that case we create an external look up relationship
so that information on the basics.
Let's go to the sales for zoo why and have a look at what external objects.
So these are the two external objects that we have artist and order the deaths.
So now what we're going to do is we are going to create a relationship between this art and order details
object so the function of the usage of these two objects is like a say for example V a place an order
online know the order book we ordered a pen and we order a shirt so all these are the order details
the pen is order detail the short is the order detail and the book is order detail and all these are
grouped under one single order Rachel.
Basically that is just a sample that I gave for you to understand how the art and object and order details
object work.
So one art record can have multiple order details in a card so in one Arda we place three different
items so those from the order details so are that a card as a pattern object and order details is the
child object so that is why we form an external look of relationship where the pattern and the child
both the external objects in our case the parent object would be orders the child object would be order
details and both the external objects and he have the matching field and parent would be the standard
external I.T. food that we have in every external object let's quickly go to the orders object and let's
have a view are the fields as you can see every external object would have the standard external light
field you wouldn't have the name feel that we have in the standard order a custom selfless objects it
would have an external 80 feet so those external light a field would be the field that the child regard
looks up to the map look parent object Ricardo that is white in external look up the matching field
and parent would be the standard external I.T. Field so now let's create a external look up relationship
between these two objects that is artist and are the details and as we already know external lookup
is also again a kind of look up relationship just acted in what external objects.
So for creating an external look up relationship what we do we go to the child object in our case it
is order details and then we would create the relationship field and as we dig for the internal lookup
relationship we already have that field in place that is the order I really feel just that it is a no
field with preloaded data we'll be converting this field to an external lookup relationship field so
he did it change the feel type choose external look up relationship
and now it is asking for the parent object.
We only have two objects another are the external objects tools orders
fill in the details here.
Please give a meaningful description.
Let me make it visible for all profiles and then the related list label.
Let me make it
external.
Order Details.
Perfect.
So now what we have done we have created a relationship field in the order details that does a child
object.
So what should ideally be created
in the child object.
Whenever we navigate to any any ID card you have this or that I defeated previously this authority field
was just a number.
But now that it is that relationship field and venue click that feel it automatically takes you to the
parent record that does or does and how are these two objects connected.
That is the orders and the order details through these standard external I do feel that standard external
I.T. field is not visible here and the UI.
So let's quickly added to the layout
just drag and drop
will affect the external ideas here so on the RDA details the the order I.D. matching with the external
i.e. off the pad and the object that does art us automatically gets mapped so every RDA list down on
the external order details within it.
So here is a related list that God gets created as soon as we created an external lookup relationship.
This is how we use the standard external field the standard external I.T. Field on the parent object
to map both the parent and the child object and this is all we create.
External look up relationship between two external objects.