Add another Group of fields

hmm .. like for the School example , it should be in the same field "School" .. Maybe the Multiple select field with the ability to add new values should be the answer for this ...

For me it would not make any sense to create individual fields per every content, but maybe i did not get it right.

for the group, no need to create another group, just store the individual data in the same field like

Record 1)

School = Teddy Newman School

Year = 2000

Grade = 3

Record 2)

School= Paris High School

Year = 1999

Grade = 2

etc

If the field does not exist in the multiple select field, just add it through the "New value" function

Currently, there are neither conditional fields, nor repeatable fields. Not sure, if Cobalt structure and logic can be extended with this kind of functionality. Would be nice... and there was already a topic/request for it.

As far as I understand your input and display, you want to enter multiple "rows" of the same 3 fields. You might use workarounds like these:

• A) as "sackgesicht" mentioned above

• B) create a fixed amount of Select fields (i.e. 5 groups, field layout in a grid-style or table, maybe with custom template and separate field output)

• C) Multi Level Select field (with Add-Your-Variants for all 3 levels, display all values in article)

• D) Relation field. Outsource all 3 education fields into an extra content-type. Set to current user. Create a simple table/list template as an override.

@stblink

How did it turn out for you? Did you have success with one of my "workarounds" ?

Hey!

Well this is an option to an yet-to-implement portal i wish to build. Since i have another project on the way its on standby.

Anyway in this case, the multi-level select would eventually work but there's a problem. For example, the grade... it's allowed for the user to search for example, which students had grade 18 at a specific class, but it does not allow the user to search students that had grades between 14-18.

So i believe the relation field would be the best case. I never used this field but for what i've seen i believe it allows to insert a type into another type.

As long as it would be also searchable, preferebly on the same "search page" would do the job.

As long as it would be also searchable, preferebly on the same "search page" would do the job.

Thanks for your infos and response. Good point: Did not test the search and filter display, yet. A very crucial question. Hopefully it works this way. Maybe dependent on the storage location (category?). Since Cobalt is multi-type friendly, I assume that there is no problem.

I still believe that the conditional fields would not be a 10% increase on Cobalt funcionality but more like 20-30%.

Rules for:

1 - option to insert button to unlock next field or next group (aka an "add another field" or "add another group of fields" button).

2 - option to unlock field X with a specific option selected

Would allow Cobalt to do anything.

Although there are more fields to improve... at my point.. more crucial for users that use Emerald.

For example i cannot limit a specific subscriber to X uploads on the images/uploads field. I can only limit the uploads applied to ALL subscribers.