Add the rich text editor control to a model-driven app (Preview)

[This topic is pre-release documentation and is subject to change.]

The rich text editor control provides the app user a WYSIWYG editing area for formatting text. The control's input and output format is HTML. The control allows copied rich text, such as from a web browser or Word, to be pasted into the control.

Some of the format options available are:

  • Bold, italic, underline, and strikethrough.
  • Text color, highlight color.
  • Font type and size.
  • Numbered lists and bulleted lists.
  • Hyperlinks.
  • Tables.
Rich text control editor in a model-driven app

Add or replace a text field for rich text editing

You can create a new text field and configure the control, or replace an existing text field. The rich text editor control can be used with single or multi-line text fields.

  1. Sign in to Power Apps. Go to Solutions, open the solution that you want, open the entity that you want, and then select the Forms tab.

  2. Select the form, and then select Edit form.

  3. In the form designer on the command bar, select Switch to classic.

  4. On the legacy form designer canvas, add or create a text field or select an existing text field, such as the account entity Description field. On the Home tab, select Change Properties.

  5. On the Field Properties page, select the Controls tab, and then select Add control.

  6. Select Rich Text Editor Control, and then select Add.

  7. Select Web, Phone, and Tablet if you want all client apps to have the ability to use rich text in the field. Then select OK to use the default rich text editor control configuration. If you want to change the rich text editor control configuration, see Rich text editor control configuration options.

    Rich text control editor configuration
  8. Save and then publish the form.

Rich text editor control configuration options

The rich text editor control comes with a rich set of configuration options that make it possible to customize its appearance, features, and behavior. To configure the rich text editor control, follow these steps:

  1. Create a JSON file that includes the defaultSupportedProps structure and configuration with the changes you want. More information: Rich text editor properties
  2. In Power Apps, create a JavaScript web resource using the JSON file created in step 1. More information: Create or edit model-driven app web resources to extend an app
  3. Open the Field Properties page for the text field with the rich text editor control, and then next to RichTextEditorControl_URL select Edit.

    Rich text editor control URL

  4. Select Bind to static value, enter the relative URL to the JavaScript web resource in the box next to SingleLine.URL, and then select OK. The relative URL is located on the web resource definition.
  5. Select OK to close the Field Properties page.
  6. On the form editor command bar, select Publish.

Rich text editor properties


You can configure all the ckEditor supported properties under this property. A few of the commonly used configurations are described here. For complete documentation about CKEditor configurations, see CKEditor.config.

Attribute Description
height Sets the height of the content editor. The default is 185 px.
font_defaultLabel Sets the default font style. The default is Segoe UI.
fontSize_defaultLabel Sets the default font size. The default is 14.
toolbarLocation The location of the user interface where the toolbar will be rendered. Supported values are top and bottom. Default is bottom.
plugins Comma-separated list of plug-ins to be used in an editor instance. Note that the actual plug-ins that are loaded might still be affected by two other settings: extraPlugins and removePlugins.
Updating this setting might remove the plug-ins from the toolbar. If you set this property to an empty string, the editor will load without the toolbar.
If you want to add one or more plug-ins to the toolbar, we recommend that you use extraPlugins. If you want to remove one or more from the default list, use removePlugins.
extraPlugins A comma-separated list of additional plug-ins to be loaded. This setting makes it easier to add new plug-ins without touching the plugins setting.
There are many plug-ins that are required for other plug-ins to work. For example, the dialog plug-in is required for the link plug-in. The rich text editor automatically adds those, and you can't override them by updating this property. This setting will simply append new plug-ins to the previous list.
If you want to remove any of the presets, we recommend that you use the removePlugins property.
removePlugins A list of plug-ins that must not be loaded. This setting makes it possible to avoid loading some plug-ins defined in the plugins/extraPlugins setting without having to touch them.


By using this property, you can write your own plug-ins and use them in the rich text editor control. Below is the schema for externalPlugins property.

"externalPlugins": [
      "name": "<<Plugin Name>>",
      "path": "<<Plugin’s folder path>>”

"externalPlugins": [
      "name": "EmbedMedia",
      "path": ""


By setting this property, you can avoid using the default entity for images so that you can enforce additional security if needed.

Attribute Description
ImageEntityName The name of the image entity.
ImageFileAttributeName The attribute name of the blob reference.


Setting this property to true will disable images. This property will have highest priority. This means that when this property is set to true, irrespective of the imageEntity property value, images will be disabled. By default, images are enabled.


By default, images will be uploaded using the client API. As soon as an image gets added to the editor, it will be uploaded to the platform. To process images, set this property to true.

Sample rich text editor configuration file

The following sample sets several of the options in the rich text editor—such as the height, location, and default font type—and uses plug-in logic. For more information about plug-ins, see Use plug-ins to extend business processes.

  "defaultSupportedProps": {
    "height": 200,
    "toolbarLocation": "bottom",
	"font_defaultLabel": "Arial",
    "fontSize_defaultLabel": "20",
    "removePlugins": "iframe",
    "extraPlugins": "uploadimage",
    "plugins": "Image"
  "externalPlugins": [
      "name": "EmbedMedia",
      "path": "/WebResources/msdyncrm_/AssistEditControl/KBEditor/libs/ckeditor/plugins/embedmedia/"
  "disableImages": true,
  "imageEntity" : {
     "imageEntityName": "msdyn_richtextfiles",
     "imageFileAttributeName": "msdyn_fileblob"

Known issue

HTML markup is displayed for fields configured to use the rich text editor control that are displayed in components other than a field on a form. For example, this occurs in views, subgrids, paginated reports, and portals.

HTML markup displayed in a field on a subgrid.

See also

Create and edit fields for Common Data Service using Power Apps portal