Current Functionality

Lookup on Standard and System objects from Custom objects

  • 16 July 2020
  • 8 replies
  • 122 views
Votes
phaneendhar_lingam
Rank
Userlevel 5
Badge

Hi team,

 

We often create custom objects to bring together data from multiple standard/ system objects for various customer usecases.

For example, to merge data from Timeline and SuccessPlan together. In these cases, we are pulling all the required fields from both Timeline and SuccessPlan objects.

Instead, if there’s a lookup on to these objects based on the GSID field, we can  pull the required fields based on the available lookups.

Our custom objects and rules become very compact if GSID is utilised fully for cases like these.

8 replies

pgeorge
Rank
Userlevel 6

@phaneendhar_lingam Most of our Standard objects are Low Volume objects.

Look ups are allowed to standard objects but the data volumes should match.

Can you let me know the standard objects you are trying to create lookups from and the volume type of your custom objects?

 

phaneendhar_lingam
Rank
Userlevel 5
Badge

I’m targeting success Plan, Call to Action, Scorecard Fact, Timeline objects - I’ll be using GSID as the lookup field. 

sai_ram
Rank
Userlevel 7
Badge +2

I’m targeting success Plan, Call to Action, Scorecard Fact, Timeline objects - I’ll be using GSID as the lookup field. 

@phaneendhar_lingam Thanks for the update! we are looking into the feasibility. I will update you here once I hear from product team. 

ssamarth
Rank
Userlevel 4

@phaneendhar_lingam  what is the volume type of your custom objects?

phaneendhar_lingam
Rank
Userlevel 5
Badge

Hi @ssamarth - These sorts of custom objects are mostly of high volume.

ssamarth
Rank
Userlevel 4

@phaneendhar_lingam Look ups are allowed between custom & standard  objects if the data volumes match of both.

sai_ram
Rank
Userlevel 7
Badge +2

@phaneendhar_lingam did you get a chance to view the comments here?

phaneendhar_lingam
Rank
Userlevel 5
Badge

Hi @ssamarth - from an implementation point of view, this is a helpful feature.  The volume of data that we handle is relatively lower (at least when compared to traditional relational databases) so it shouldn’t be a problem.

Reply


Terms & ConditionsCookie settings