Anomaly found on CMS for both the data not showing correctly

[Sai1278]

Hi Adobe Family,
we report an anomaly found on AEM for both the "xyz project" and "zyx project" nodes (both dev and qa). When we select the content list view, we display the info columns for each node with the wrong header, therefore not corresponding to the data in the column. For example, in the "Published" column we display the content templates, in the "Template" column there is no information, in the "Modified" column there is information about the publication instead of the modification. 

[EstebanBustamante]

Hi,

First, let's determine if this issue is specific to projects "xyz" and "zyx." If it is, then the problem might be limited to those projects. However, if the issue persists across the entire instance, it could indicate a broader problem with the entire system.

Have you recently upgraded AEM or performed any significant operations? Changes like these could potentially affect the functionality of the platform.

Additionally, I recommend checking the browser console and error logs for any relevant error messages. This information can provide valuable insights into what might be causing the issue. Any additional details you can provide would be greatly appreciated.

Hope this helps

[Sai1278]

Hi @EstebanBustamante 
It has come to our attention that all environments are experiencing a particular issue, despite no recent updates being made to Adobe Experience Manager (AEM). Surprisingly, there are no console errors being reported.

[EstebanBustamante]

Hi, 

Did you try to replicate the issue without your codebase? To make sure is AEM related and not your custom code?

I could not reproduce the issue (Using AEM6.5.16)

[Sai1278]

Hi @EstebanBustamante 
I checked the codebase, and @arunpatidar  mentioned a way as well, but the issue was still reproduced. AEM version: 6.5 with SP 15 currently in use.

[Sai1278]

Please give me some guidance
@arunpatidar Jörg_Hoh
aanchal-sikka
lukasz-m
SureshDhulipudi

Imran__Khan

Raja_Reddy

[arunpatidar]

Hi @Sai1278 
What AEM version are you using?

Can you please also try in vanilla instance without your code?

[Sai1278]

Hi @arunpatidar 
The AEM version was 6.5

[arunpatidar]

Hi @Sai1278 

I am on AEM 6.5.16

I can see all the values as expected.

did you tried in vanilla instance with we.retail code?

[Sai1278]

Hi @arunpatidar 
I tried and getting same result. Please refer ss

[arunpatidar]

Hi @Sai1278 
I think the Operation is messing up with the ordering. What I can see in our instances Operation as the last as per list

[Sai1278]

what will do in these scenario

[arunpatidar]

Hi @Sai1278 
Can you please check following for below path

/libs/wcm/core/content/coral/common/configurecolumnsdialog/items/form/items/chooseColumns/datasource

1. did you override either above path ? or cq/gui/components/siteadmin/admin/listview/columns/datasources/availablecolumnsdatasource in apps

2. what do you see at /libs/wcm/core/content/common/availablecolumns or is there override in apps for this path

For me datasource contains following nodes

[Sai1278]

Hi @arunpatidar Yes, I noticed that you mentioned the previous comment. Recently, no one has modified anything, and everything is showing correctly. But why is the data not displaying properly?

[arunpatidar]

There might be some overlays in /apps path. Please chekc there as well.

If the node structure is correct in /libs then definitely someone deplyoed/changed something in your environment.
Could be third party package.

[Sai1278]

@arunpatidar Thanks for Your support.

[Raja_Reddy · Accepted solution]

Hi @Sai1278 

Please compare the following paths:

1. /apps/wcm/core/content/common/availablecolumns
2. /libs/wcm/core/content/common/availablecolumns

Are the data and nodes the same, or are there any extra nodes? This might be the issue. I think there are some extra nodes in the /apps/wcm/core/content/common/availablecolumns section.

[Sai1278]

Hi @Raja_Reddy 
Thanks for your support. I understand now. I have removed the extra node, and it is displaying correctly.