Ability to delete properties when they are still being used in views
Currently I'm running into the issue that i cannot delete an old property, when they are still being used in a view. As a superadmin, I'd like to have the possibility to overrule this and delete this anyway.
Because I'm not able to edit the view that is managed by another user (of which I also cannot see which user) and delete this property from their view.
Yes it's impossible to delete / remove custom company, customer, deal list views even as a super admin to be able to remove properties that are using them. Very frustrating.
Yes, I am having a similar problem. The values in the drop-down of our property need to be edited monthly. I used to be able to go in and delete them with no issues, but suddenly I cannot. It needs to go back to the way it was for the last 5 years. If I have to delete that value from contacts, then I lose all of that historical data.
Agree with above, there are some historical properties that are used in over 100 views and deleting those views is not an option, as people might still be using them, but the older property is no longer required and to go and edit every single one of those views is simply unrealistic. As a superadmin you should be able to just acknowledge that the property is being used in views and click archive and remove from all views and be done with it. Trying to clean-up the amount of properties, but the functionality makes everything too manual and could really do with this upgrade
Yes! I have super admin access but can't remove a property that is in a view...from folks who don't even work at our organization any more. It's cluttering up our database for sure.
We are running into this problem as well. To make matters worse, it's nearly impossible to determine who owns the view. It seems like super admins should have the ability to remove the property from any views it's used in. We have completed unused properties with no values that somone put into a view because it sounded similar to the property they were looking for, and now we can't remove them.
This would be a great feature. Currently I need to ask users to change their own views, or clone/delete them but then they are created in my name which isn't ideal.
I'm Shay, a Product Manager here at HubSpot. I am hoping to set up a few calls to discuss this issue. If you have time soon, please grab some time on my calendar using mymeeting link.
I wish I could upvote this more than once. It simply doesn't make sense that super admins cannot delete/archive properties when they are simply used in views AND that we cannot remove the properties from said views either.
As a broader frustration, I need to update a property type for a pretty commonly used property and it's used in 59 places. This is very time-consuming to acheive changing a freetext property to a dropdown select. The process of removing it from everywhere, while I get the requirement, there must be a better way.
@Peter__Jones I have the same problem. It's great that Hubspot has introduced new property types and validation rules, but in reality it's only useful if you're a new customer. I have properties tied to literally hundreds of workflows, lists, reports, views etc. and the fact that a property needs to be completely clear of use before you can change it makes it a no-go (the same effort would be required to create a new property and move everything across).
That said, being able to delete properties that are used in views is a pretty low-risk activity (worst that could happen is that the user that created the view doesn't see the property!) so this would be a great start to solve the wider issue.
@shajones I tried to book you but the link is not available.
This is really annoying, while I understand the need to have it removed if used in a workflow, I don't really understand the need to remove it from report and views, because these sometimes are created by other users so I would need to impersonate (triggering a notification) each one of them to get the property unused and to be able to remove it. As super admin I should be able to delete it in any case.
