Rich Text Editor Control on Custom Page

(0) Share

Report

Posted on by CU08122123-0

Hi there

I have recently finished building a custom page for my model driven app.

This page contains 3 forms, one of which uses a Rich Text control.

This page worked perfectly for a few days and then suddenly stopped working after a series of Microsoft solution updates in my environments (this issue is replicable across both Dev and UAT).

In the app designer, the component displays as expected:

However, when opening it in my model driven app, I see the following:

Looking through the logs in the dev tools console, I see the following error:
ckeditor.js:370 [CKEDITOR]: The license key is missing or invalid.
If you suddenly started to see this message, this may mean you accidentally updated CKEditor 4 to the LTS version (4.23.0 and above). This version of the editor is under commercial terms and requires acquiring an "Extended Support Model" contract - https://ckeditor.com/ckeditor-4-support/
For more information about this error go to https://ckeditor.com/docs/ckeditor4/latest/guide/dev_errors.html#invalid-lts-license-key

Sounds to me like MS upgraded to a new version of the rich text control by mistake and have broken rich text controls in apps?

Has anyone experienced this too? Any suggestions?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

developerAJ 4,763 on at

Like (0)

Report
Copy link

Link copied!

please help us with the custom page code

Seems like you have used CKeditor packages in your code and they are paid for some of the modules and error is because of it either you buy a subscription from them [CKEditor 4 | Visual Text Editor for HTML] or change the code

Was this reply helpful? Yes No
CU08122123-0 18 on at

Like (0)

Report
Copy link

Link copied!
Hi @developerAJ

Thanks for your response. I have used the standard out of the box rich text control in this page.

Since posting this question, I have done some investigation and the problem occurs only when the rich text control is opened in a popup through JavaScript.

The problem does not occur when the control renders on a standard page.

My repro steps:

Create a new custom page

Add a table to the editing studio (for a table that contains a multiline rich text comment)

Add a form for the table onto the page and add the rich text field.

Unlock the data card, delete the simple text input and insert a Rich text editor input control instead.

Wire up the rich text to output its HTML to the DataCard

Save and publish

Create a new ribbon button on an entity and add the following code to call the page

async function openRespondCompletePage(formContext) { Xrm.Utility.showProgressIndicator("Launching Responder..."); const criteriaId = formContext.data.entity.getId().replace("{", "").replace("}", ""); const customPageOptions = { name: "fp_criteriaportalcommentcreator_da7b7", // <-Your custom page schema name goes here recordId: criteriaId, pageType: "custom" } const navigationOptions = { target: 2, } Xrm.Utility.closeProgressIndicator(); await Xrm.Navigation.navigateTo(customPageOptions, navigationOptions); formContext.data.refresh(true); }

Click the button to open the page

Expected: The rich text control renders

Actual: The render error in my original post appears.

It seems that when the popup opens, the rich text control loses it's licensing scope and breaks

Was this reply helpful? Yes No
Verified answer

CU08122123-0 18 on at

Like (0)

Report
Copy link

Link copied!

Looks like Microsoft worked out that they broke it and it has now been resolved - can no longer reproduce the issue

Was this reply helpful? Yes No