Hi @jessica-s there are a few different ways to approach this. One would be to create a stand alone record for Condition events, linked back to the related Objects. The benefit of this design is only having to enter the info once, rather than multiple times on each object record. Several of our museum users take this approach.
I should add that this design only makes sense when a single condition event is shared between multiple objects, and it is less useful in the scenario when one object has 10 condition checks.
For the latter it would help to make the container you've configured a bit more readable by changing the "max columns" settings for the lists. If you set "max columns" to 5 for the first and 3 for the second, they will only take up one line each in the container. This may help address your readability concern.
@samrahman Yes, you can easily set a <br> tag as the delimiter between repeats of the container in the report, breaking each condition onto it's own line. This would also work for the standalone record, which would be a relationship to the object, delimited by line breaks.
You could approximate that with formatting, but from a conceptual stand point, each "row" is a single record in our framework. We don't break out repeating metadata (i.e. in search results) as multiple rows corresponding to a single object.
Hello. I have a condition container that contains text and containers. I added 2 records but only the first one is showing. Any ideas what I could be doing wrong? I've read the display template guide to help me build the code below. Thanks