In that case, you don't want to store those additional properties under the component content. Instead of keeping them in the component content, I would read them from the location where the datasource is populating the selection drop-down.    sample pseudo codein component sling model PostConstruct...

@Giuderos Why would you want to store the name and description properties in the content along with id? Is it simply because you need to read them and display them in the UI? 

 Yes, you can enable the debug logging for dispatcher. Change the value of the DISP_LOG_LEVEL to Debug in global.vars file located under conf.d/variables and run the deployment.    Define DISP_LOG_LEVEL Debug  

Hi @Sean-McK,    I'm guessing you're missing the cq namespace tag in your file.   Do you see the tag namespace for cq at the jcr:root node in experienceFragmentsIndex-3-custom-1/.content.xml file? If you don't see it at the jcr:root node, you can add the below to fix the build issue. xmlns:cq="http:...

Default dispatcher files should not be edited in Cloud Service, and default_filters.any is one of them. Instead, you can add those rules to the filters.any file and test the querybuilder in non-production instances.   In case you've not noticed, there is a text block like the one below mentioned in ...

What are the versions of BPA and AEM? Are you evaluating the current instance to transition to AEM as a Cloud Service?    I ask the above questions because core components in AEM as a cloud service are available in /libs. You will see the above error if you're running a BPA version that checks cloud...

You can add users and groups to the following config that needs web console access   http://localhost:4502/system/console/configMgr/org.apache.sling.extensions.webconsolesecurityprovider.internal.SlingWebConsoleSecurityProvider

Yes. @sdouglasmc, deleting the package from the install folder uninstalls the content, which is also valid for Service Packs.

You can't delete it after the installation. JCRInstaller service watches for any changes in the install and config directories and updates the repository state.   As @Saravanan_Dharmaraj tested, package will be removed from repository if you delete it. 

Hi @jamiec4451712    Check your project modules pom.xml files have correct packageType mentioned as per the documentation - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/aem-project-content-package-structure.html?lang=en#xml-package-types   ...