How to save a large form with nesting in Bitrix?

S

Sergey2020-07-30 01:05:51

1C-Bitrix

Sergey, 2020-07-30 01:05:51

Hello. Faced a very complex, but at the same time simple problem.
The task is to save a huge form from the frontend (filled in by the user in his personal account) to the Bitrix admin panel and so that it can be edited through the admin panel.

The structure of the form is as follows:
Create a project .. it has a name, a date and a few more simple fields.
Further, this project is added to its participants , there can be many participants.
Each participant , in addition to his name, date of birth, has the ability to add an infinite number of fields to indicate social networks.
Further, the project fills in a few more static fields according to the type of description, and so on.
That's whyproject , you can specify goals , the number of goals is also not limited ...
and stuff like that ... the form is very huge ..

I don’t understand how to save all this and where.
Let's say the project is one element in the infoblock, simple fields are additional properties, you can also add goals through multiple fields, etc., but how to store participants? Multiple fields are no longer suitable, because each participant has several fields + added fields for social networks.

There was an idea to store participants with their multiple fields in json format, but then the content manager in the admin panel will not be able to edit these fields in any way. Or to score on the admin panel and tell the manager to edit through the front?

Please help with advice on how to store it all and where.

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

A

Alexander Vorobyov, 2020-07-30
@BXVoral

So keep the participants in another infoblock. And communication using a multiple field of the type binding to the elements of the infoblock

F

Forever Extreme, 2020-07-30
@vechnokrainii

The project itself can be thrown into the info block with all its fields. If there are many goals in theory, then you can throw them into a highloadblock and then bind them to the infoblock field.
The same goes for the participants. You enter them in another infoblock, and by id you associate them with hl (for example, the same social networks)