In the object analyzer, we are not showing the dependent jobs if the field was selected from the lookup object.
Ex: In the below fetch is created on GS relationship object and we added in Account owner id field from the lookup object account.
So when you check the dependency for Account owner id, the above rule was not showing in dependent jobs list.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
+1 Definitely need better dependency reporting. I know Gainsight Analyzer can be helpful here but it can take quite some time to click around and dig into each field and it’s associated objects, etc.
Hi@rajasekhar_parasu @ana_g
We have added the request to our roadmap and are analyzing it currently.
I’m not sure if this is the exact same issue or a separate idea, but I received word from Gainsight Support today that Lookup fields are not supported in Object Analyzer data flow diagrams, but they really need to be!!! This is wildly inhibiting when attempting to make full use of Object Analyzer, and often leaves me using Data Management dependencies instead which are not as easy or visual to use.
Note from GS Support:
One thing I would like to commend GS Support for is confirming that this is expected behavior that is not outlined in their documentation & pushing a note to the correct team to get this explicitly outlined in their documentation. Looking forward to seeing this updated!
Either way, if I am changing the CSM field using Rules Engine, I’d love to be able to see the rule loading the Company → CSM field value in Object Analyzer. It doesn’t make any sense to me why lookup fields were omitted from this feature’s design.