I’ve worked with Gainsight(GS) product since 2015. There have been many upon many product decisions across the last 9 years that have not made sense to me; let’s roll out new features instead of fixing/improving our existing features(who doesn’t like having inactive options in their DropDowns for their end users to see, Why would you want the ability to create SP views to guide your end users to focus for work, or even something as simple as I want to report on the most recent timeline entry and when it occurred without having to run a DataDesigner or Rule?
However, most of them, when thought in a different way can be made sense of or why it is not happening right now.
This is the lesson I have learned working with/providing feedback with product.
I draw the line when features/capabilities are being taken away to meet the, not even end users UI but the admin UI.
Essentially since the admin UI for some reason couldn’t be modified to accurate display preview of a data we’ll simple remove a capability previous allotted to admins and call it a day?
Just to provide context around this. We have a simple rule where we want to push the most recent timeline entry made on a R360/C360 to the actual Company or Relationship Record. How do you do this? Well you fetch timeline entries by Rel and/or Co record. Then you max the activity date, which is a date time. Then you merge that max with the initial timeline fetch, merge of the CO/Rel GSID and Activity datetime. Oh wait, you can’t do that anymore!
Wow are you kidding? This design decision makes 0 sense. Merging on datetime was the only way to get to the most recently created/updated record!!
Please bring this back!
Also can someone on community team please change this to an Idea?
I had a ticket open for 2.5 months for exactly this… I was seeing records in the Merge preview, but the output was empty.
Today it was closed as “resolved”, super happy (and naive) me went to work on the design and got the wonderful surprise of realizing that the datetime fields weren’t even appearing to merge by them…
I wholeheartedly agree with you. How is taking away a feature/functionality away an acceptable “fix”?
Done@darkknight
Hi@Wayne and all,
We do remove some features that are unused and not needed form time to time. I can assure you that we did not decide / plan to deprecate this feature from the same lens. For a bug fix, some wrong decision might have been taken by a teammate. We will review internally and come back on this.
Meanwhile appreciate some patience here.
Thanks for the quick response@rakesh . I may have been a bit hasty and/or blunt.
But, I think there are just two key factors I find disappointing in this decision.
Again, sorry for the call out. But, there should be checks and balances emplaced to prevent things like this. Especially with HRE being such a touchy subject already, not that this is HRE independent. But, I think there are even still some bionic to HRE gaps that haven’t been addressed.
...implemented and it was/is no where to be seen in the release notes. So now I’m wondering what else is released under the hood that is not ever listed out? Having to find small changes like this out from happenstance and sometimes luckily from Community Admins is not the correct route.
Preach!
I also use(d) this functionality frequently when trying to find the MAX date of something. Agree with all the points here. It’s definitely a surprise when something that was previously possible has been removed with no notification. Understand that not all features are used by everyone, but at the very least, would be good to notify those that are using said feature.
what…. i have multiple rules like this. now I need to go back and see if it is broken
Curious why features/options are being removed to begin with (especially features or options that would be used in logical arguments, whether in rules, queries, etc.), and without including the community. If it’s part of the conversion to the Horizon featureset, I can understand that the product might change, but logical operators and options seem like something that should only be added to, not removed. And should be the same across the product.
Seems like a perfect type of thing to run by the product council!
This is honestly insane - it just broke the rule. My merge field is now null without any warning - the rule has been running and no error.
CC:@Paulina
...implemented and it was/is no where to be seen in the release notes. So now I’m wondering what else is released under the hood that is not ever listed out? Having to find small changes like this out from happenstance and sometimes luckily from Community Admins is not the correct route.
Preach!
I have a Community post in the Product Council space (at least I assume it is still there, I can’t seem to find it) titled “How often does this happen?”. Gainsters - Please read this (or if you’re a current Council member), this is the same type of problem, and that post is coming on 2 years old. Even then it wasn’t a ‘new’ problem.
This has to be a bug that should get fixed ASAP - we also have existing rules relying on this functionality
This is honestly insane - it just broke the rule. My merge field is now null without any warning - the rule has been running and no error.
CC:@Paulina
Just for the record, we’re seeing the same UI bug. However, it does still seem to be executing successfully. At least for us.
Thanks@rakesh and team!!!
Can anyone confirm for me which day/time this issue started?