I am building an application describing jobs and skills. Each job has a list of skills, which I defined in option sets. I want to build an RG that lists all the skills for a given job in the same cell (in-line, one after the other), rather than by rows and columns. Here is the targeted design:
Hi there, @jonathan.pinet⌠someone had the same question (or at least a very similar one) a few days ago, and that thread resurfaced another thread that you might want to check out.
If youâre using the new layout engine (new responsive engine), thereâs also this approach, which involves a simple CSS tweak to a regular RG. Hereâs the result.
In your case, the âtag cloudâ RG would be nested within a cell of your main RG. In that case, youâd need to tweak the CSS to target the inner RG properly. If you need a working example of that, let me know.
Hi again @sudsy, thanks for sharing the ressource. I implemented on my page and it seems to work well, except that items are not wrapping when reducing the page width (an horizontal scrollbar appears, which I donât want).
See my list:
Just to cover the bases, do you have the element id option enabled in your app settings? (Settings â General â Expose the option to add an ID attribute to HTML elements)
If you do that and assign the rg-cell-wrap ID to your main (outer) RG, then youâll have to tweak the CSS to target the inner (nested) RG. I think something like the following should workâŚ
#rg-cell-wrap .RepeatingGroup {
display: flex;
flex-wrap: wrap;
height: auto !important;
min-height: auto !important;
}
That should apply the CSS to the inner RG instead of the main RG. (Note that the rg-cell-wrap ID needs to be added to the outer RG. Donât include the # symbol when you enter the ID into the property editor.)
Seems like @NigelG has an even simpler solution though.
EDIT
One final note⌠In my working example, the CSS is included in an HTML element which accompanies the RG. Thatâs done for ease of distribution. However, it should ideally be included at the page or app level of your app. You donât want/need the CSS to be output in each cell.
Thatâs what I was missing! It works now, thanks so much for your help @sudsy
Thanks also @NigelG - thatâs a good trick to know for future instances!
Here is a link to my tutorial on how to do it in the old responsive engine
In the new responsive engine, I would follow the approach listed in this forum post as it doesnât require HTML elements making it much easier to trigger workflows and conditionals when the tags/chips are clicked etc.