As I’ve honed and redesigned our internal tool on bubble over the years, I’ve made several changes to data structure. As a result, many data types have fields that are no longer used on the front end and which I no longer need to interact with when building, but may contain data in old database entries. It would be nice to have either an archive feature or a hide/show toggle so that we can limit the fields that are displayed when writing expressions.
Edit: This would also be useful for data types and pages. My current workaround is to rename them with “z_arch_” at the beginning of the string so that they’re sorted to the bottom of lists.
I’m not sure this is a great idea. In Bubble, people generally expect to be able to see and reference all fields on a thing. If a field is hidden, the assumption will usually be “this field doesn’t exist” or “something’s broken,” not “it’s archived.”
Renaming with a prefix actually solves that pretty cleanly by keeping everything discoverable without getting in the way.
And if a field truly isn’t needed anymore, even if there’s legacy data in it, it should probably just be deletable. In the rare case that the data somehow matters, you can always migrate it to a log or history type with a quick WFOL before removing the field (and all its value).
