I just ran into a scenario where I had to change a field that was selected in a bionic rule after the rule had already been created. All I needed to do was remove a field and add a different one.
This required me to:
Remove field from action.
Remove field from 2 Merges.
Remove field from 'Show field' from original dataset.
Add new field to 'Show Field'.
Add new field to 2 merges.
Add new field to action.
This seems like a LOT of work just to change one field. I understand that I would be required to add the new field throughout, but could we allow a user to remove a field from the 'Show Field' section and then state ' This field will be removed from the following sections'? This would drastically reduce the number of steps needed to complete this action.
Open to other suggestions but this seemed very cumbersome/confusing.
Thanks!
Hi Zach,
I agree. Deletion of field from all tasks is a cumbersome process. Cascade deletion of fields from a rule is already part of the roadmap and will definitely be implemented based on priority. I will keep you posted on this.
Regards,
Jitin
I agree. Deletion of field from all tasks is a cumbersome process. Cascade deletion of fields from a rule is already part of the roadmap and will definitely be implemented based on priority. I will keep you posted on this.
Regards,
Jitin
Reply
Sign up
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.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.