@Shashi_Mulugu @krati_garg  Thanks for your inputs. Our code creates content fragments and their variations and then populates their element values. If I call .listAllVariations() and get the variationDefinition, I will still need to call getElements as it's not the title/description of the variatio...

Hi Currently we have code to programmatically create a content fragment with variations. The process is: 1. create content fragment 2. create content fragment variation and populate all the variation elements by calling the createVariation method below:   public static void createVariation(ContentFr...

Thanks smacdonald2008​. I've raised this issue with customer support and am awaiting their response.  Incidentally, it appears if we create the parsys items (eg text) under the itemX node. The parsys items will also get wiped out everytime we update ANY fields in the dialog.  The multifield doesn't ...

The problem is that you are not creating your parsys node as a child of your multifield nodes.You can use pure htl to solve this without using use classes.<sly data-sly-test="${resource.hasChildren}" data-sly-list="${resource.listChildren}">  <sly data-sly-test="${item.hasChildren && item.name=='tab...