So this can't be done with anything other than Eclipse? The folks on StackOverflow seemed to believe that VLT should do the trick, but I saw the same thing you did, smacdonald2008​. I saw a bunch of nodes and therefore nothing I could use in code.

I just used the Dialog Conversion Tool to convert a design dialog from Classic to Touch UI as part of a 6.1 to 6.3 upgrade. Now I need to export the proper XML or folder structure to add that to the codebase. What's the proper way to do that? This is where I'm running into trouble. I've tried using ...

I finally found an example that works. Not sure what the difference is between that and earlier examples I've tried, even using Coral 3. In the example I got working locally I changed the resourceType of only the multifield and its children. Should the entirety of my custom component use Coral 3?   ...

himanshusinghal​, That's the version of ACS Commons I'm using. Is there some kind of incompatibility with other commonly used libraries I should be aware of? Basically it writes the data to the datastore correctly, but it can't be retrieved when clicking back into "configure".     

And to be clear, smacdonald2008​, your solution (reading the article) is only if you don't want to use acs-commons, correct?

The article at aemcq5tutorials purports to work under 6.3 and it uses standard granite? Do I have to convert everything to coral 3 if I use the coral versions?    

Is there a specific version of ACS Commons that works? I've followed this example exactly and when I go to back into the component to configure it (after initially configuring it) no data is brought back. It's there. I can see it in CRXDE Lite, but it doesn't populate the dialogue when I try to edit...

A follow up to this. While the core component worked, it came with some difficulties. Mainly that the tooltip was a different style from the other tooltips in the dialog and so it scrolled off the page. Eventually I was able to get the standard granite fileupload component (granite/ui/components/fou...

I'm working on a 6.1 to 6.3 upgrade and every custom component we've written that uses a multifield is failing under 6.3. The "add field" button works. The data gets saved to the datastore. But the data can't be retrieved on edit. Here's the cq dialog xml code.<?xml version="1.0" encoding="UTF-8"?><...

We have a number of custom multifield components all written for AEM 6.1 and using JSP. Is there any reason those need to be converted to HTL? They're not working currently under AEM 6.3.