Skip to main content
kytpowell
Contributor ⭐️⭐️⭐️
Feb 23, 2021 10:49 PM UTC
Solved

Best Practice for Improving Data Anomolies

I am trying to understand the best practice around limiting the number of Data Anomolies we have, specifically with the number of accounts with no customer info value. I know that it can occur with validation rule errors that impact Gainsight from updating the CustomerInfo field, but it is happening on a large number of accounts and then impacting the creating of new Relationships.

Besides going in and manually fixing each record is there a best practice around getting to the root of the problem so it lessens?

gopal_rao_kallepu
gopal_rao_kallepuAnswer
Helper ⭐️⭐️⭐️
Mar 1, 2021 9:20 AM UTC

@kytpowell as you rightly said these kinds of data anamolies arise due to complex trigger flow and validation rules. We suggest you to review the validation rules and triggers on your Account object if the data anomalies are frequent. Please reach out to our support if the problem persists, to help us understand your org set up better.

Gopal
View in thread

2 replies

sai_ram
sai_ram
Expert ⭐️⭐️
Feb 24, 2021 5:55 PM UTC

@kytpowell Thanks for sharing your query here. Its been long time I had hands-on this area. I will check on this and get back to you. 

Translate
gopal_rao_kallepu
gopal_rao_kallepuAnswer
Helper ⭐️⭐️⭐️
Mar 1, 2021 9:20 AM UTC

@kytpowell as you rightly said these kinds of data anamolies arise due to complex trigger flow and validation rules. We suggest you to review the validation rules and triggers on your Account object if the data anomalies are frequent. Please reach out to our support if the problem persists, to help us understand your org set up better.

Translate
Gopal
    Terms & ConditionsAccessibility statement