ערוך

שתף באמצעות

Tutorial: Configure the rich text editor control on Power Pages

  • מאמר

In the tutorial, you'll configure the rich text editor component on a Microsoft Dataverse form, and enable the rich text editor to be visible on a webpage.

This tutorial will use the Feedback table and the Contact us webpage that is available in the Starter layout templates.

Prerequisites

  • Your portal version must be 9.4.3.x or later.
  • A site using one of the Starter layout templates.

Step 1. Add the code component to a field in a form

  1. In the design studio, select the Data workspace.

  2. Select the Feedback table.

  3. Select Forms and then choose to edit the simple contact us form.

  4. Select the Message field.

  5. Choose + Component and select the Number input component.

    Add RTE component to form.

  6. Select Done.

  7. Select Save and Publish form.

Step 2. Configure the rich text editor component on webpage

In the following steps we will configure the existing feedback page, you can also create your own page and add your own form component.

  1. In the Pages workspace, select the Contact us page.

  2. The Message field should appear on the form with the message Enable custom component to see this field in preview.

  3. Select the field and choose Edit field.

  4. Select the Enable custom component field.

    Enable RTE component in design studio.

  5. Select OK.

  6. Select Sync.

Note

To display the data as rich text, you might have to increase the character size of the text columns to accommodate the extra information.

Step 3.1 Add table permissions for the rich text attachment table

For using and storing images in the rich text editor on the portal, you'll need to add table permissions to the rich text attachment table (msdyn_richtextfile).

  1. Open the design studio and select Set up workspace.

  2. Select Table permissions.

  3. Select + New permission to create a new table permission for the rich text attachment table. The name can be anything you choose; in this example, we use RTE Attachment.

  4. For Access type, select Global access.

    Note

    The Global access type is chosen because no relationship exists between the table configured to use the rich text editor control and the rich text attachment table.

  5. Under Permission to, select the Read, Write, Create, and Delete checkboxes.

  6. Assign an appropriate web role to the table permission.

    Configuration of the rich text table permissions.

Important

If you want to store images as base 64 strings directly in the column that you've configured to use the rich text editor control, you need to configure the control by using a JSON configuration file. Set disableImages and disableDefaultImageProcessing to true to allow images to be rendered consistently across all clients. Using this method doesn't require the global table permission on the rich text attachment (msdyn_richtextfile) table.

Step 3.2. Add web API site setting

In order to save images in the rich text editor control, you will need to add a couple of site settings.

  1. Open the Portals Management app.

  2. Go to Site Settings.

  3. Create the following site settings: enter the name, your website, and the value of true, and then select Save & Close.

    Site setting name Value
    Webapi/msdyn_richtextfile/enabled true
    Webapi/msdyn_richtextfile/fields *

Step 4. Preview the site.

  1. In the design studio, select Sync.

  2. Select Preview and then select Desktop, go to the Contact us page, you should see the custom component enabled.

    RTE component on a form.

Rich text editor on a read-only form

On a read-only form, the rich text editor displays the content with formatting and images. The content can be read, but not edited or updated.

Note

Only .PNG, .JPG., or .GIF file formats are supported for drag and drop.

Rendering rich text editor content field using liquid or Pages Web API

The rich text editor content field can be rendered using Liquid or the Pages Web API. If the field contains any image files, they will have a Dataverse Web API reference path. To display these images on a Pages web page, you need to replace the current path with the corresponding Pages API path.

Example :

The image element within the rich text editor content field will be displayed as follows, containing a reference to the Dataverse Web API path:

   <img loading="lazy" src="/api/data/v9.0/msdyn_richtextfiles(d0a473a4-9e95-ee11-be37-000d3a5c393e)/msdyn_imageblob/$value?size=full" style="height:61px; width:376px">

To update the image element, replace /api/data/v9.0 with /_api as shown below:

   <img loading="lazy" src="/_api/msdyn_richtextfiles(d0a473a4-9e95-ee11-be37-000d3a5c393e)/msdyn_imageblob/$value?size=full" style="height:61px; width:376px">

See also