Dynamic Content - CrossCategories & CrossLink
Vasiliy Gorodeckiy
Hi! There is no automatic linking between dynamic content elements.
For example:
- I add a case, add the "result" field in it
- I attach the result field to the "Result" category element
- I indicate this result in the case
Next, I expect this case to be linked to the result.
But this is not happening! The "Result" element does not refer link to cases. This has to be done with your hands again.
All semantic connections and interrelations need to be put down by hand in each category (collection).
What's the point? This does not simplify the filling of the database in any way.
Atick Eashrak Shuvo
Accepted AnswerHello Vasiliy,
Thank you for your feedback, and sorry for the inconvenience you're experiencing.
The behavior you described is expected. Our Dynamic Content system functions similarly to a relational database, where each content type (or "collection") maintains its own records and relationships. Links between items are intentionally one-directional; when you connect a "Result" to a "Case," the "Case" knows about the "Result," but the reverse link isn't automatically created.
This design ensures better data integrity, flexibility, and performance when managing large datasets. Automatically creating two-way links could introduce circular references, performance slowdowns, and difficulties in maintaining data consistency during updates or deletions.
We understand that manually linking related items can be time-consuming. We'll share your feedback with our product team for future consideration, as improving usability while maintaining database stability is always a priority.
Thank you again for taking the time to explain your use case. We appreciate your patience and understanding.
Best regards