RELATED IDEAS
Assign Custom fields to a parent workspace
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace.
If we could have the ability to define which workspace needs particular custom fields it would eliminate the noise everyone else sees.
Understood. The issue is that our workspace has been added after Aha! has been implemented elsewhere within the company. For example there are 5 fields called "Client", yet each one has different definition but there is no way to associate it or filter it within a workspace. Today we have to add all 5 of those fields to a filter, see the results and based on that start removing the ones we don't need. This gets very tedious when almost every fields has 5+ copies of it.
Thank you for the additional context. We originally allowed custom fields to be configured at the workspace level. However this created big headaches for customers. In particular that if you needed to use the same field in multiple workspaces, you could not consolidate the data into a single column in reports.
A potential future improvement here could be to filter down the set of options shown when adding a filter based on the workspace selected. We will continue to monitor feedback on this idea.
In the meantime, I did want to point out that setting an internal name for your custom fields will help your situation right away. The internal name will show up in parenthesis when adding a field or filter to help you identify the right field in situations where there must be duplicates. When editing a custom field, select Show advanced options and you will see the Internal name field.
Custom fields are showing in reports and filters. We want to be able to reduce the noise and only see what is applicable to our parent workspace. If there are 10 other workspaces there should be no need to for us to see their fields. Often times they are duplicate as well and we can't easily determine what is a "our field" or one someone in another unrelated workspace created.
Hi there, thank you for your request. I just wanted to clarify one thing. Is your request specific to custom fields showing up in reporting fields and filters? I just wanted to be sure you were not also having issues where custom fields were showing up on record drawers and details pages in every workspace. Thanks!