Hide specific property options from users (in the portal, and not only in the forms) and still be able to report on these options or select them in the workflows
Background
we want to hide specific options to users from further use, as they are not relevant anymore. At the same time, we're not able to map them to any new/other options so we would like to 'archive' them but the records would still keep these old values.
Problem
the reporting filtering for a dropdown property allows for selecting only the currently available items and there is no option to select these deleted. Like a free text "contains" value.
Potential solutions
1. (optimal) add an option to hide an option from users (similarly to "In Forms" setting for an item)
2. set the options that should be currently used and available in the property settings. And in the report filters & workflow trigger options to have all options visible - the list of items that would consist of currently used and all unique that are currently set in any of the records
3. To give the option in the report filters to set a free text value for "contains" instead of a requirement to select from the shortlist
This is so important for our end-user experience! When values for dropdown fields change over time, we want to avoid having users scroll through irrelevant options to find the one they need. When is this happening HubSpot?
We need this!! We register who the Sales Engineer is on each deal and obviously there is turnover. We don't want the old SE to be an option but don't want to lose the fact that they worked on specific deals while they were with us.
+1 when doing some optimization of the CRM we often run into the issue of wanting to archive an option or create a "hidden" option on one of the dropdowns to store values that are no longer going to be used going forward but still need to be tracked/reported on historically. It's a huge hindrance and data nightmare to try to create a workaround for this, which seems like it would be so necessary for so many companies doing the same thing.
I really need the feature to hide old options in a property. Our process requires us to add options to a property over time, so without the ability to hide options, users face significant difficulties in updating data and management. Additionally, if the new option is very similar to the old option, the issue of searching and selecting also poses risks for us. I hope HubSpot will soon support this feature.
Strongly agree! We have so many properties (or property values) which are no longer used or needed, but we still need to keep them for reporting and historical data. There should definitely be a way to hide a property or property values so that they are no longer visible to end users, but still available on the backend for workflows & reports. Without this, it's impossible to keep a clean portal.
Would really appreciate the option to disable/hide options for a Dropbox. That way we don't lose data and prevent users from continuing to use an old option.
The new form tool have own options for visible selections in the drop downs, but no function available for hiding selections in the in app forms. This is a big problem for us tagging deals with product areas when we have selections in the properties for inactive offers we no longer distribute but need for history and statistics.
This is an absolute must have for an enterprise CRM. We need to retain the historical field values but deactivate from being selected by our users. Especially for Deal properties where data changes from year to year. I work primarily with nonprofits and not being able to change what Funds are available to assign donations to over time leads to incredibly messy dropdowns.
How can this still not be implemented. No changes to the underlying datamodelling. Solely a mark for the option not to be avaiable for CRM users from some date (hence to end-date it) and then implement that in the user interface to not show it.
This is basic stuff in any CRM system (or any business critical system, really).
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.
