Skip to main content
keith_mattes
Helper ⭐️⭐️
March 9, 2021
New Idea

Admin QOL: Full Dependency Report

  • March 9, 2021
  • 17 replies
  • 235 views

When working in Data Management and attempting to obliterate an improper or vestigial field it would be nice to have a FULL dependency report to help admins locate every spot they need to modify in order to remove the field.

Currently, this only works for one selection at a time and each time you want to investigate where a dependency is, you need to re-input the Field in the top right drop down.

BONUS POINTS: We have an automatic dependency interface/report that allows us to selectively remove a field from multiple areas at once or “Remove all” so the Admin doesn’t have to go to every item (similar to company merge/show all fields). (yes this is very complex)

17 replies

gunjanm
Expert ⭐️
March 25, 2021

Success Plans and C360 Summary too.

@dan_ahrens @minh_phan here’s something that really needs to move to the top of the pile.  It’s so easy to inadvertently break things without being able to fully identify dependencies throughout the product.

This bit me hard today because post-NXT migration we had duplicate user lookup paths on our Company object (that no one explained would happen - pre-existing SFDC ID lookups and new GSID lookups)

To reduce confusion and complexity, I’ve been working on trying to swap everything out from the SFDC ID lookup path to the GSID lookup path and was relying on Dependencies (and Analyzer) to help with that effort.

Well, it turns out I missed some places...and so when I deleted one of the SFDC ID lookup paths (which Data Management let me do):

  • The entire C360 Summary stopped displaying (because it was being used as a field on the Summary that I had forgotten) and our users thought Gainsight was down (why would the whole section vanish?)
     

     

  • A Data Designer set freaked out and said ALL fields were removed from a dataset (until I just removed the one Lookup field and saved the set)
  • Success Plans stopped displaying on C360 (just displayed as below - which is astounding..why would the entire Success Plan stop displaying) because it was being used on an SP layout.
  • ALL 16 Dashboard Filters from a dashboard vanished because ONE report was pointing to the old field path in ONE of the Dashboard Filters (also inexplicable - why would they ALL disappear?):
    Broken view
    Fixed view
  • A Journey Program produced an error because it was being used in a query (fortunately only as a show field and nowhere else)

We really should be able to easily (and trustworthily) identify everywhere fields are being used throughout the product and be prevented from shooting ourselves in the foot.

 

I feel heartburn just reading this. 

  
End Proctoring-
 
Gunjan
dan_ahrens
Expert ⭐️⭐️⭐️
March 26, 2021

Thanks for sharing this feedback @keith_mattes and @darkknight . Simplification of the admin experience is definitely something that is top of mind for us this year. Samarth (who posted above) is the lead PM on this area of the product, so it’s good that he has eyes on this. :)

VP of Customer Success at Forcepoint
Helper ⭐️
March 29, 2021

This might just be at the top of my list, that is how life-changing this would be.

Anastassia Goidina
bradley
Expert ⭐️
November 3, 2021

Adding to this that different views consuming fields that create dependencies should be covered as well - e.g. GS Home custom views, renewal center views, etc.

Helper ⭐️⭐️⭐️
January 10, 2022

 

Hi all,

 

Happy to let you all know, with the dependencies UX revamp - all the dependencies for a field will be displayed at one place. This enhancement will be released in Jan’22 RT.

 

Thanks,

Bhawya

 

jparker
Contributor ⭐️⭐️⭐️⭐️⭐️
April 7, 2022

Hi @Bhawya 

The new Data Management dependency checker still doesn’t seem to include Journey Orchestrator dependencies

Is this going to be included too?

Looking for my next role: Gainsight Lead / CS Ops Product Council Member. Let's connect: https://www.linkedin.com/in/jon-parker/
bradley
Expert ⭐️
April 7, 2022

Linking to this post I made earlier as well: