How to add objects to the directory via Edit-in-Place in UMI?

Have a service Catalog. Each service has a number of stages, and their number ±10pc. Each stage has 4 fields. To do it 40 fields in object properties is not rational.
Solution: add in the directory object field: a Dropdown list with multiple choices to bind to the directory with the desired set of fields, and link them.
Problem: adding entries to the directory it is easiest to do via the frontend using Edit-in-Place.
I tried to do this:
<section class="steps" umi:element-id="{$pid}" umi:module="catalog" umi:field-name="steps" umi:region="list" umi:type-id="141">

 <article umi:region="row">
 <h4 umi:type-id="141" umi:empty="Title" umi:field-name="name"></h4>
</article>
</section>

Doesn't work: the field names in common, for example, he substitutes the name title. If you use unique names, it says that the field is not found (on the page that it is not). If you use the popup method of adding, then display the form with the right fields, but does not save, swears on absence of the Header in the request to create the object.

Maybe there are other solutions to the problem?
July 9th 19 at 13:46
1 answer
July 9th 19 at 13:48
To do it 40 fields in object properties is not rational.

It is rational, because UMI.CMS separately stores the schema of the data (Template data type) and data (the objects), it remains to solve the issue the interface for this will be useful to use the possibility of customization of the system which is Overloading templates administrative interface or through the front-end that will be even easier to implement.

Solution: add in the directory object field: a Dropdown list with multiple choices to bind to the directory with the desired set of fields, and link them.


If I correctly understood, this decision is no different from the version when creating deep or flat hierarchy of data types for objects.

Doesn't work: the field names in common, for example, he substitutes the name title.


Problem solution not described in enough detail, I suppose that problem is in data view as the basis of a recorded name of a dictionary element, if I have correctly identified the problem, according to everything will be clear.
Actually no. This is certainly the simplest solution, but it is also the most stupid. If tomorrow the need for a pair of objects to make 20 steps?
I like that option has already been considered :) I do not want to do that, if there is a normal solution. - nikita.Stracke commented on July 9th 19 at 13:51
: added to the answer, and if tomorrow the need for a pair of objects to make 20 stages, it's much more effective to create a child type of object with 40 stages they will be added to the new data type will only have to add another 20 stages, the important thing is that they will not interfere with each other. - Arne.Altenwerth63 commented on July 9th 19 at 13:54

Find more questions by tags UMI.CMS