Now that we have understood in detail about the various type of relationships they extend and look up
the Internet look up how do we do the configuration and setup.
Let's take a quick look at some of the considerations and the restrictions that we have while using
external objects and says force.
The first one only look up external look up an indirect look up relationships are available for the
external objects.
No other relationship types of supporting we are well aware of this.
All right.
So whenever we create relationships on the external objects we can only create the lookup external lookup
or the indirect lookup.
Say for example we can consider the external object orders.
So what we did is we basically changed the field type right.
So now if I tried to change the field type I can see only the look up external look up and the indirect
lookup.
These are the three options that are available you cannot create a master detail many too many and all
of us using external objects
depending upon the availability of the external system of related list of child external objects may
load slowly and use this view the pattern recorded and be just perfect.
So as we have established a connection between Salesforce and the legacy system and if the PAN and object
is a standard object in our case like a call so intimately a goal for a particular apparent guard we
see all the related child records in the related list so one of the considerations that we need to have
this does in a later list may load a little slower slowly than usual depending upon the availability
of the external system okay.
Moving on Cascade delete isn't available for external object relationships.
We know that Cascade delete automatically happens and master detailed relationships and it does not
happen and look up relationships.
However in Luke loving relationship that is an option that we can request for Cascade delete.
But for that we have to contact says we'll support what he had for external objects.
That option is not available.
Moving on the external look up an indirect look up relationships the pattern that a guard up is applicable
link in the relationship field of the child.
So our first relationship that we created was indirect look up in that Collins was the bat and object
and art as was the child object.
So then you pick any child that God the parent card appears as applicable link.
So basically you can click on that particular record and that will automatically take you to the parent.
But what we have to note here is that if a user who is accessing the child in a car does not have access
to the banner in a car then in that case it will not appear.
SS click on the link.
So that it goes it says the child a guard is viewed by a user who does not have access to the phantom
guard the fan and get caught up in the relationship field as just plain text insert often link
the next consideration is look up filters are not available for external look up and relationship feels
so lovingly created I look up a relationship feel the option of look up filters wasn't available let's
again recall the feeling that we created in the art as object.
This was the relationship field that we created.
So let me hit the edit button and now you can see that the all the details that are available for us
created and you can see that the lookup filter is not available.
But then we generally create to look up a relationship or I will let a look up relationship or a master
data.
Then we have that option of lookup filters that we can filter out the values of the look up.
But that option lookup filters is not available when we use external objects
only objects that have a custom field with external lady and unique attributes are available as bad
and objects in indirect lookup relationship.
If you do not see your desired object then you create an indirect lookup.
Then there is a possibility that there are no unique external I.T. fields available in that object.
Meaning they normally create indirect look up a relationship.
So in either case we created an indirect look of relationship between icons and artist.
So for that we basically converted this particular field doing direct lookup field.
So let me shoot.
They did button and let me give a change field type and here it is already in direct lookup I'm just
like want to show you so indirect look up and step two is to choose the related object.
Basically the bat and object in this scenario if you see one account does listed out here right.
That are more the standard of custom objects listed here.
Why.
Because only objects that have unique external I feel will be listed out here.
So off all the objects that we have a number of icon does that only object that has this custom unique
external I.T. Field.
So that is the reason only a code does listed here.
So for experimenting mode what you can do is you can create the unique external I.T. fields in other
custom or standard objects and you can see if it is getting listed out here and in real time if your
desired object is not updating over here the chances are that there are more unique external I.T. fields
available in that object.
So first create that field and then create this relationship.
Perfect.
So this is one of the catch you once and then about the case sensitivity.
So if the external column name is case sensitive make sure that the pattern objects custom field is
also marked case sensitive.
We know that that option off Case Sensitive is available.
For us in sales force.
So make sure that you make the pattern objects fields also extra case sensitive.
Because basically those two fields will be matched the value from the child object that is the external
object will be matched that does external lady field in the painting object.
So if one is case sensitive also make the other one case sensitive so that the matching will happen.
So these are some of the considerations that we need to have in mind like using external objects and
since force.