Thanks @BrianKasingli and @sarav_prakash for the responses. I had a priority change and have not gotten back to this. I am hopeful that the solution has been provided, but unfortunately have not had a chance to try it yet.

We have an already-built component that utilizes a third party JavaScript API. There is a textfield property entered by a content author that is ultimately read by the JavaScript API to display a message. The property is stored in a data-* attribute in the HTML. We want to change the textfield to a ...

Agreed @AEM_PARTY ! Content authoring Search and Replace just feels like something that should be available in a high-end, advanced tool like AEM without developers writing a script. A rudimentary version of it exists in the classic UI, but was never re-created in Standard (touch) UI.Some use cases:...

There is a simple work around to this issue. Add a _DocumentRef to the GraphQL query. It feels like a strange approach but it does work! Query{ imageTestList{ items{ title image1{ ... on ImageRef { _path _publishUrl } ... on DocumentRef {...

Created a Content Fragment Model and used a Content Reference data type. The "Accept only specified content types" is set to Image. When using the model to create a Content Fragment, it works to select typical image types such as PNG, JPG and SVG. However if a SVG is selected the GraphQL query does ...

In the event someone runs across this and is curious:I contacted support and opened a case. They have duplicated the issue and acknowledged it as a bug. They are not committing to a time for resolution but it will be considered during development cycles.

When looking at Content Fragments in List View with Content Fragment Model column enabled sorting based on Content Fragment Model does not work. The sorting control exist but it appears to sort based on Created date rather on Content Fragment Model. If sorting is selected, regardless of ascending or...

Grrrr. This appears in Adobe Experience Manager Assets. How do I move it to Adobe Experience Manager. Grr.

The way the list of components is displayed in Author changed with the Cumulative Fix Pack 4.  The list is now stacked per component with component icon on top of component name on top of component group.  Prior to the Fix Pack it was simply the icon beside the component name (component group did no...

This has been resolved with a call to technical support.  The environment in question was in-place upgraded from AEM 6.1 to AEM 6.4.  Starting in AEM 6.3 the Crypto Keys are stored in the file system by default.  Prior, the keys were stored in the repository.  Because this system was in-place upgrad...