Skip to main content
kelly
Helper ⭐️⭐️⭐️
August 17, 2018

Notify when bionic query becomes invalid due to changes in Salesforce configuration

  • August 17, 2018
  • 3 replies
  • 39 views
If changes to a Salesforce field structure are made so that the bionic query is no longer valid, it should create an error or some sort of notification. 

This week we experienced a change in our Salesforce instance with a value that existed as a drop down value and became its own field as a checkbox. For example, the query was Role = Project Manager. Project Manager has been removed from the drop down values and now exists independently as Project Manager = true.

If you look at the query in the live AO, the value is now blank but if you were to try to save a draft version with a blank value you can't - [i]it has to have a value. The rule should not continue to run successfully when the filters are no longer valid.

    3 replies

    samantha_braastad
    Contributor ⭐️⭐️⭐️⭐️⭐️
    August 20, 2018
    Agreed! Our company is going to be reviewing our entire Salesforce instance and this would be hugely beneficial for catching anything that slips through the cracks.
    faust_belarmino
    Helper ⭐️⭐️
    August 20, 2018
    YES! This has been a pain to workaround... out team just audited and deleted a bunch of Salesforce fields and it was a pain to review and make sure rules weren't failing when fields were deleted...
    darkknight
    Expert ⭐️
    August 21, 2018
    Gainsight - this feels like a bug.  In Kelly's example above, clearly the filter criteria options are no longer present (for whatever reason).  If it won't save the query without having that value populated, then this should result in a failed rule and notification sent if that value is no longer populated.
    Jeff Kirkpatrick