Hi All
I am trying to learn this new form component and went thru docs/IU however I need support in figuring out how to store form information when its submitted.
I have to build 50+ forms so please advise scalable solution to store, view and access these forms in an easy manner.
Write the information to a database.
The scalability is going to be highly dependent on the commonality between the 50+ forms and your database design, not the submission form.
1 Like
I’m working on a similar project where users can dynamically build forms and then save them to a database. From what I’ve gathered, the best approach is to store the form definition in the same JSON-like format it’s generated in.
My current plan is to extract the form configuration directly from columns.items and store it as a blob (or JSON column) in a SQL database. This preserves the structure exactly as the user created it and makes it easy to re-enter into a form later.
That’s the approach I’m using, and it seems like it should work well for your scenario too.
4 Likes
You make a very valid point that keeping the original json data intact could be useful (and efficient).
When I think about storing json data my mind automatically goes to MongoDB instead of a traditional SQL database. Mongo is specifically made to work with json data and would probably pair well with Ignition forms.
Competent SQL databases have json column types. Like PostgreSQL. Just say no to Mongo.
2 Likes
I didn’t know that was a thing. Very cool.
Thanks for mentioning it. I have some ideas.