Ir al contenido principal

Making multiple edits using AEM's Bulk Editor - Tips and Tricks

Here are some tips and tricks about Adobe Experience Manager's Bulk Editor with some usage scenarios, above is the vid and below you will find some useful notes.
  • The Bulk Editor allows you to make several content changes at once without having to go page by page using the siteadmin or sites console or node by node using crx de lite.

  • In this Tips and Tricks video I show you a couple of scenarios like:

    How to replace the Resource Type for pages and components when you renamed a component or template

  • Add content into multiple instances of a component inside a page when you have to update several pieces of content and you already have them on a spreadsheet for example

  1. 1.

    Pre-reqs

    • Have access to an Adobe Experience Manager instance
  2. 2.

    Using different query parameters

    • Inside AEM 6.2 you can look directly for the resource type
          aem-bulk-changes-examples/components/structure/page
      
          "sling:resourceType":aem-bulk-changes-examples/components/structure/page
      
          "resourceType":aem-bulk-changes-examples/components/structure/page
      
      You can also search for a partial match
          resourceType:aem-bulk-changes-examples/components/
      
    • In aem 6.3 or 6.4 given that this won’t work, you can use a different query parameter that might return what you need. Bear in mind that some properties won't work as you might expect, like, searching using the jcr:primaryType, in this case you have to just say "type" instead and then it will work. Also if the property has a colon as part of it use quotes around them.
          type:"cq:PageContent"
      
          type:"nt:unstructured"
      
    • You can also mix multiple query parameters, in this case it will try to find nodes that math both query parameters
          type:"nt:unstructured", "sling:resourceType":aem-bulk-changes-examples/components/structure/page
      
  3. 3.

    Adding Custom Properties to the results

    • You can add the properties that you want to be able to modify, here you have to use the complete name.
          cq:template
      
          jcr:primaryType
      
    • You can include more that one column/property too
          cq:template,order,newText
      
  4. 4.

    Enabling the import button

    • To enable the import button on the bulk editor just add “hib=false” into the url, this will instruct AEM to show the import button,
          ?hib=false
      
    • Don't forget to add the root path used for exporting the tsv file
  5. 5.

Comentarios

  1. Other than "type" have you found any other query keys that work?

    ResponderEliminar
  2. why would they remove sling:resourceType as a query parameter? need that the most right now. is there no other way to query for this?

    ResponderEliminar

Publicar un comentario

Entradas populares de este blog

Create a custom AEM workflow process step with a dialog

In this tutorial I talk about how to create a custom workflow step process with an additional dialog for configuring it, above is the vid and below you will find some useful notes. 1. Pre-reqs Have access to an Adobe Experience Manager instance. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2. What is an AEM Workflow and workflow model Workflows allow you to automate different tasks inside AEM by defining a s

How to create an AEM component using Reactjs

In this tutorial, I will show how to use use Adobe's archetype to create an AEM application with React.js support and also how to add a new React.js component so that it can be added into a page, above is the vid and below you will find some useful notes. In the second part we will see how to configure the Sling Model for the AEM React component. 1. Pre-reqs Have access to an Adobe Experience Manager instance. You will need aem 6.4 Service Pack 2 or newer. Have Maven installed, understand how it works and also understand how to use Adobe's archetype, you can watch my video about maven here: Creating an AEM application using Maven and Adobe's archetype 2.

Creating Docker containers for Adobe Experience Manager

This is a Docker tutorial for creating a docker image for the Galen framework, above is the vid and below you will find some of the steps followed. Adobe experience manager is a content management system which in a nutshell is an application that allows us to create web sites to be consumed by end users. You might be familiar with other such applications like wordpress or drupal which serves the same purpose A typical deployment would be comprised of two AEM instances, the author instance used for creating and modifying content, the publish instance which serves the content and finally we have a dispatcher which is a static web server used for caching, load balancing and some security purposes. We can configure an AEM instance to work as an author or publish instance by either changing the file name