Enforce SFDC referential constraints within Gainsight lookup fields

Hi Josh,

I agree, we are planning to fix this by spring release.

Thanks,
Nitisha

While I agree that linking a CTA to an Opp would most often happen within the same Account -- this is typical and should be the default -- I would be cautious about being too rigid here.  Indeed, it can easily happen that an Opportunity is on the 'wrong' account, especially with renewal Opps.  

Consider the following:  a large Corporation includes many Companies inside it (think: Disney Corp includes Disney Theme Parks, ESPN, etc.).  A business Relationship may be with one of these companies but the Contract may be held at a parent or even a 'sibling' company.  (Some corporations have separate IT Companies that often hold contracts.)  From a Finance perspective it can be important that a Renewal Opportunity be on the Account that holds the contract.  But this might be totally irrelevant from a Sales or CSM perspective.  So you could definitely have a situation of a CTA on a Customer  -- the one that actually uses the product -- which makes sense to link to an Opportunity on a different Account -- the one that pays for the product.

Broadening the discussion a bit, this difference in what makes sense from a Finance, Sales and CSM perspective, is a really common challenge.  It is what so often leads people to say things like 'our hierarchy is broken.'  Thing is, rigid constructs like Accounts and Hierarchies simply can't model the variety of things that you need to model to satisfy all of the important perspectives on your customers.  (Which is 'right', orienting by Users, by Buyers or by Payers?  Really, all of them!)  This is part of the motivation for our Relationships capability.  Instead of running around and trying to agree on some phantom 'correct' Account structure, just keep things simple at the Account level and model the different perspectives with Relationships (of different Types).  And because the core concept in Relationships is *association* rather than *hierarchy* you have huge flexibility to link things together in ways that capture what is true about how you relate to the customer. 

Hi,

We do honor Acount Id filter while searching for records to link to a CTA( Search performed with Name and Account Id combination except for Case where case number is used instead of name). This is the whole reason why we ask to select Account reference field to be used in Cockpit configuration if there are multiple Account lookups for the linked object .

Thanks,
Srinivas

Hi, I have a contact lookup field in the C360 Attributes section and our end users are unable to find the admin quickly because we have so many contacts. Is there any way that this request can be revived?