I don't mean "forms" as in WebFroms. I mean forms in the general sense, like a Vacation Form or Meeting Form.

We currently uses SharePoint to manage all the forms that we need to fill out.

I am thinking of taking the initiative and learning more about .NET Core and converting these forms to an actual system with a better workflow.

One area I'm stuck on is how to define each field in the form.

When I started learning, I would define each field as a separate column in the database (e.g. name, email, effective date, etc...). Then if I ever needed to add or remove fields, I would need to run a migration.

The problem is that our forms frequently change. In Sharepoint, it was simple to add and remove fields.

But having to run and test a migration to the database every time feels slow.

Is there a better way to do it?

I was searching around, and Stratusforms did something neat. Granted, it's for Sharepoint only, but the idea is that they only had a single column, and all the "fields" were JSON. So you could keep the database structure the same, and just add or remove fields by updating the JSON only.

Is there something similar to this for .NET Core?

Or am I using the wrong database? (I'm using SQL Server to test). Should I be using something like Mongo or perhaps Postgres's document features?

Any advice or pointers would be appreciated. Thank you.