Dialog Changes and Data 'Loss' | Community
Skip to main content
Level 2
Apr 4, 2019 6:49 PM UTC
Solved

Dialog Changes and Data 'Loss'

I have a handful of components that are currently using acs-commons to store multifields as json. I've started moving the components away from acs-commons and I noticed that any change I make to an existing cq:dialog node makes the previous data irretrievable by the Touch UI Dialog when using the editor. Am I missing something to have this not happen? Or is there a way for me to convert the json stored to a node structure?

Please let me know if I have not explained well enough.

Thanks

EDIT: I found this link and maybe it is what I should be using?
Dialog Conversion Tool

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
arunpatidar
arunpatidarAccepted solution
New Participant
Apr 5, 2019 12:01 AM UTC

Hi,

The dialog conversion tool helps you to convert dialog from classic or/to coral2 to coarl3 UI.

It won't help you to recover content.

To get data populated when converting of Coarl2 multifield to Coarl3 multifield, you must convert JSON into nodes.

With the help of JCR API, you can parse JSON and create nodes where ever your content is used inside /content/site.

Arun Patidar

1 reply

arunpatidar
arunpatidarAccepted solution
New Participant
Apr 5, 2019 12:01 AM UTC

Hi,

The dialog conversion tool helps you to convert dialog from classic or/to coral2 to coarl3 UI.

It won't help you to recover content.

To get data populated when converting of Coarl2 multifield to Coarl3 multifield, you must convert JSON into nodes.

With the help of JCR API, you can parse JSON and create nodes where ever your content is used inside /content/site.

Translate
Arun Patidar