Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Touch dialog multifield nodes rename after dialog save

Avatar

Avatar
Level 1
tarunrajg
Level 1

Likes

0 likes

Total Posts

8 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
tarunrajg
Level 1

Likes

0 likes

Total Posts

8 posts

Correct Reply

0 solutions
View profile
tarunrajg
Level 1

19-10-2020

Hi,

We are migrating from AEM 6.1 to 6.5. So the authoring for existing pages is done in classic UI. 

Here there are few config pages where the content is referred across the sites.

The config pages have multifield components in it. When the authoring was done in classic ui for the multi field values where re-ordering of fields have taken place, the node names were not saved in order. 

for ex: when i initially save the dialog, the nodes would save as item0,item1 ,item2. When i again open the dialog in classic ui and re-order the multifields, the nodes would save as item0,item2 and item1.

So this is the case for all the existing pages. The pages referring the values from these config pages are done via the nodes name.

Now if I open the dialog in touch UI and save the dialog without any changes, the nodes will be saved as item0,item1,item2.

So if a page is referring item2 of config page would now refer a different node after dialog saved in touch ui.

Is there any way to handle this usecase. Any suggestions are welcomed.

Is there a way to stop renaming the nodes after dialog save in touch ui? As even in 6.5 classic ui the node names are not changing after re-arranging the multi filed values.

View Entire Topic

Avatar

Avatar
Validate 1
Level 2
a74048191r
Level 2

Likes

6 likes

Total Posts

17 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Validate 1
Level 2
a74048191r
Level 2

Likes

6 likes

Total Posts

17 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 5
Boost 3
View profile
a74048191r
Level 2

20-10-2020

Depending on the extent of what needs to be updated, try writing a utility servlet that 1) reads your 6.1 ordered nodes into an array - item0, item2, item1. 2) deletes the nodes in the repository then 3) reads the nodes from the array and saves them back to the repository as item0, item1, item2. You could accept parameters such as page name, resourceType, node name to have some control over what's getting updated.  You would run this once to prep your data for the 6.5 migration 

 

Thanks!