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.
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?
I’m targeting success Plan, Call to Action, Scorecard Fact, Timeline objects - I’ll be using GSID as the lookup field.
I’m targeting success Plan, Call to Action, Scorecard Fact, Timeline objects - I’ll be using GSID as the lookup field.
Hi@ssamarth - These sorts of custom objects are mostly of high volume.
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.