Multifield component with custom xtype .. cached?

Question

I am working on a MutliField component with a Custom Xtype, so our author can create a list of YouTube videos for a built-in playlist.  I created a component called videoplaylistmultifield that just contains a single js file which builds the fields and registers the xtype and inside my Video component dialog, it uses this xtype.  The issue is, I want to update the fields, but AEM seems to be retaining an old version of the xtype component.  I can even delete the entire xtype component from crx and when I go to edit the Video Component, it still shows the old fields.  Is there somewhere in AEM that may cache the JS file for my xtype component?   I am still on AEM 6.1 sadly.

kylew87495614 · Accepted Answer

smac, I don't really have a choice right now - I have to use classic. Hopefully my company will let us upgrade to 6.3 and use touch soon.

I found out the problem though, so for anyone else that may or may not experience something similar:
My AEM is having some issues invalidating cache for clientlibs. I've noticed it happen with a few components, and I've simply deleted the generated folder. However, for my xtype stuff, there is no generated folder. So I found running the script at this URL solved my issue: http://localhost:4502/libs/granite/ui/content/dumplibs.rebuild.html

smacdonald2008 · Answer

I am glad that you got this working. When you move to Touch UI, we have many HELPX articles that show you how to work with Multifields in AEM Touch UI.

See:

Scott's Digital Community: Creating a HTL Repeating Data Set 6.3 Component that uses Sling Models

Building Experience Manager Components using Granite/Coral Resource Types

Adobe Experience Manager Help | Creating an AEM 6.2 HTML Template Language component that uses a Multi-Field dialog