I am trying to use “Secure Rich Text editor” from the constellation UI gallery , inside an embedded data table view , but the data entered is not saved when we click “save for later” , i have also tried other components as simple as a text input and it does not work , how ever it works outside of the embedded data, how to make use of editable custom dx components inside the embedded data view ?
This issue usually happens because editable custom DX components inside Embedded Data views in Constellation do not automatically persist values correctly in repeating row contexts. I tested the “Secure Rich Text Editor” and even simple Text Input components inside an embedded data table, and the entered values were not retained after clicking “Save for later”, while the same components worked correctly outside the embedded data context. In embedded tables, components work differently compared to normal case-level views, and maintaining only local component state may not properly sync the data back to the case model. Currently, inline editable custom DX components inside repeating embedded data views seem to have some limitations in Constellation. Using the component inside a Details View or modal for the embedded row appears to be a more stable approach.
![]()
After Save for later the data is disappearing as shown in the above Image.As an alternative approach, instead of using the component directly inside the table row, try opening the embedded data row in a Details View or modal and use the editable component there, which seems to be a more stable and supported approach in Constellation.
Thanks , currently we have hard requirement to use it as inline edit , @Kamil_Janeczek / @MarcCheong is there any way we can tweak the “Secure Rich text” editor react code to handle this ?
The Secure Rich Text Editor is part of our open source github repository - you can raise issues and enhancement requests via that project.
As @Sohan_Reddy_Anugu has suggested, I would be doing Table with Modal here. Even without your issues on the component, large chunks of text inside a table aren’t a great UX



