"Draft" entity per user per database

Ideas & Features
1

This is a proposed solution for this: "Filters aren’t applied because they have missing ‘𝑥’ dynamic values"

I understand that the core issue is that the entity does not exist, and hence the data can not be filtered on something that doesn’t exist yet. What if every time someone goes to create an entity, it creates a “draft” entity under the hood (if any values are not empty). This has the upside of allowing the dynamic filters + also saving inputs. So if I start creating an entity, then leave the form to check something, when I come back it is still there. Two birds with one stone.

Considerations:

  1. Unique and Required fields need to be ignored in drafts, only checked when trying to submit. I think it would need a duplicate table per fibery table under the hood. Task would need a Task_Draft with the same schema, but with no constraints. Then the draft data is saved there. It would make things more complex, and not sure about the performance implications of doubling the number of tables per workspace, but it would be a potential solution I think!
  2. Public forms. Currently values do get saved, but not sure how that works. My guess is it’s local and not saved to a DB. This would need to change to allow dynamic values in public forms.
2

This is not the only reason for the issue. In some cases, e.g. buttons as action items in a view, the dynamic filter is not available because the filter is operating on an array of items (even if the array sometimes only has one element)

3

Makes sense, mainly this issue is for “Update” operations, correct?

That would need separate ideation for a solution, but it’s both these issues that make it difficult, right?