Also, I was trying to display a dynamic table that automatically appends submitted fields (From formelements_DM to the end of the table. My approach was to use bindings to save the inputs (formelements_DM) in another Documentmodel (AllEntries_DM). How can I achieve this behavior using only the Content Model?
Thanks for your question. We’ve been in contact regarding this issue and a bug ticket (A12-18140) has been raised relating to your first point.
Labels in Dynamic Content Models
The issue here relates to the Content Model Preview.
In the experimental Content Model Editor the Preview has been extended to allow you to use dynamic elements that reference Document Model Fields. The Field Labels added in the Document Model or in the Content Model should be displayed in the Content Model Canvas and in the Preview. However, when using locales other than “en”, you see some issues:
“de” Labels are shown in the Canvas and in the Preview App
“de” Labels are not shown in the Content Model Preview
Labels from other locales are not shown in the Canvas or Content Model Preview. The Preview App uses the default locales of “en” and “de” so other locales are not testable.
Whilst it’s frustrating that the Content Model isn’t rendered how you would expect it to be, the fact that “en” and “de” locales are both working in the Preview App suggests that everything will be okay in production. Have you tested you models in your Project Template based application where all the relevant locales are present?
Workaround
You can test all Field Labels in the Document Model Editor. Select the Fields and start Ad Hoc Testing. As the localized labels are added here, testing in the Document MOdel Editor makes sense.
Dynamic Tables
I think you are trying to achieve something like this:
Use a Repeatable Group Element to show repeatable data
Present completed rows as row only
Present a single editable row which can be used to append data
If this is the case, I would approach this in the same way that I would approach using Filter Expressions for Form Model Repeats. Basically, create a Field Value that can be used to determine if this row should be editable or not. Then use two separate areas in the model to model the read-only and editable sections.
You can use Conditional Elements in combination with the Repeatable Group Element to do this. How about something like this?
You need to use the Project Template to be able to start customizing your code. Check our the Documentation and Development Tutorials for more information.
Hello @julius-low-kernel, I am a member of the Discourse team. I can see that there was a new response to your question on Missing Labels in my Content model. Do you find it helpful, or should the question remain open?
Thanks ahead for your feedback and have a nice rest of the day!
