This looks like a rendering limitation with stored Base64 image content in the Constellation Rich Text Editor, not a save problem.
can you check if the raw saved HTML in the data type and confirm whether the ‘img’ tag is still intact when you reopen the record and whether the image source is a true Base64 data URI and not truncated or escaped during save/load and also compare behaviour with an uploaded image URL versus inline Base64, since Base64 images are often the part that fails in rich text editors.
A better approach is to avoid storing Base64 images inline in the Rich Text Editor for Constellation if you need stable reopen/edit behaviour. Instead, store the image as an uploaded file/attachment or a media reference or an external image URL and then reference it in the rich text content.
Hi,Thanks for checking. I also reviewed the raw HTML stored in the data object and observed that the tag remains present after reopening, and the image source is still stored as a Base64 data URI. From what I can see, the content is not being completely removed during save.
However, I noticed an additional behavior that may help narrow down the issue:
If I enter content in the format: Text → Image1 → Text → Image2
After saving and reopening the record, only the content up to Image1 is retained in the stored raw HTML.
The second image and any content after it are not present.
On reopening, the first image is displayed as a black/blank image, and the remaining content is missing.
This makes it appear that Constellation Rich Text Editor is not handling multiple inline Base64 images correctly during save/load and/or rendering. Since the first tag and Base64 data are still present in the stored content, it seems more like a rendering or content-processing limitation than a simple save issue.
I understand the recommendation to use attachments, media references, or external image URLs. However, in my case, the client requirement is to support inline images directly within the Rich Text Editor content, so using attachments or external image references is unfortunately not an option.
Hi Venakt, I faced the similar issue and below is the solution for this issue.
Root Cause
The property configured as a Rich Text Editor field is currently limited to 256 characters by default. Since the raw data contains a significantly larger amount of content, the field is truncating the data and not storing the complete value. This is causing the discrepancy that we are seeing.
Resolution
Increase the length of the property to accommodate the expected data size (for example, 50,000 characters or higher, based on business requirements). Once the column size is updated, upload the image/content again and verify the results.
Steps to Update the Column Length
Navigate to Configure → System → Database → Schema Tools.
Select the appropriate Database.
Choose the relevant Table and Column.
Update the Column Length to the desired value (e.g., 50,000 or more).
Save the changes and perform the upload again.
After increasing the column length, the Rich Text Editor field should be able to store the complete content without truncation, resolving the issue.