Page Editor Consistency Errors

Introduction

In this document, we explain how to solve the most common or complicated consistency errors that can occur when configuring pages in Studio Pro. An example of a consistency error on a page is when you do not specify the entity property of a data view on a page.

Some errors have error codes and if these errors are described in documentation, Studio Pro has a clickable link to the corresponding document. Others do not have an error code, in this case, you can manually search whether a particular error is described in documentation (you can search by a message you see in the Errors pane).

List View Consistency Errors

If you do not configure a data source for a list view properly, you will get consistency errors.

The scheme below shows that the data source of the list view has been set to Database, but the entity that needs to be retrieved from the database has not been specified. This results in a consistency error.

The table below describes the most common errors which can occur when configuring a list view, the causes of these errors, and ways to fix them.

Data View Consistency Errors

If you do not configure a data source for a data view properly, you will get consistency errors.

For example, you have selected Listen to widget as the data source, but you have not selected the specific List widget you are listening to.

The table below describes the most common errors you can come across when configuring a data view, causes of these errors, and ways to fix them.

Context Not Available Consistency Errors

The errors that you can get when a page or snippet is expecting a context that is unavailable are described in the table below.

Error Fix Example for CE1568

When a page expects a context that is not passed to it from a calling page or a microflow, you will get consistency errors.

For example, the Customers page contains a list view with a list of all customer names (Customer is set as Entity in the Data Source properties), and a Details button outside of the list view (placed in a container only). The Details button opens a Customer Details page when a user clicks it (the On Click Action for the button is set to Page).

However, the Customer Details page has a data view that expects an object Customer to be passed to it. In other words, this page needs to get data first to be able to display it.

As this object is not passed to it from the Customers page, you get a consistency error.

As the Details button to the Customers page is outside a data container, it does not know which object to pass. The way of fixing this error depends on the following:

• You want to pass a specific Customer object from the Customer list to the Customer Details page, in other words, the details of a particular customer will be displayed on the Customer Details page (for more information, see the Passing a Specific Object to the Page section)
• You want to create a new object of the Customer type and pass it to the Customer Details page, this means that a new customer will be created (for more information, see the Creating a New Object and Passing it to the Page section)

Passing a Specific Object to the Page

If you want the Customer Details page to open the details of a specific customer, this means you want to pass a specific object to the page. As we already have a list view with the customers list on the Customer page, we can fix this error the following way:

1. Open the Customers page.

2. Drag the Details button inside the list view.

   

Now the button gets the object of type Customer from the list view on the Customers page, and it will be passed to the Customer Details page. As a result, the details of a particular customer is displayed on the Customer Details page.

Creating a New Object and Passing it to the Page

If you want to create a new customer and fill in the customer’s details on the Customers Details page, you can do the following:

1. Open the Customers page.

2. Open properties for the Details button, and set Create Object as an On Click Action.

3. Set Customer as Entity.

4. Set Customer Details as Page.

   

5. Change the button’s caption from Details to Add, as this button will now create a new customer instead of showing the details of an existing customer.

Now when a user clicks this button, the Customer Details page will open, and the new Customer object will be created.

Data Consistency Errors

When a widget that expects as object from its data source does not get it or gets an object from a different entity type, it causes errors in data consistency.

Some of the most common errors of this type are described in the table below:

Error Fix Example for CE1573

When you set a microflow or a nanoflow as an on-click event for a widget, and this microflow expects an argument (for example, an object) that is not available, this will result in an error.

For example, on a page named Customers you have a button that calls a microflow (that is an On click event of the button is set to Microflow).

However, the microflow contains a parameter Customer:

The microflow parameter expects an argument Customer, and since this argument is not available on the page where the button is located, it results in an error.

To fix it, do the following:

1. Open the Customers page and drag a data container onto it. For example, you can drag and drop a list view.

2. Set the data source type of the list view to Database and set Entity (path) to Customer.

   

3. Place the button inside the list view.

Now the Customer object is available on the page and it matches the microflow parameter Customer.

Error Fix Example for CE1574

When you set a microflow or nanoflow as an on-click event for a widget, and this microflow/nanoflow expects a certain argument, but a different argument is available to the widget, this will result in an error.

For example, on a page named Customers you have a button that calls a microflow (that is an On click event of the button is set to Microflow).

The microflow contains a parameter Customer:

On the Customers page you also have a data container, for example, a data view, that has an object Photo available. That means that the data source type of the data view is set to Context and Entity (path) is set to Photo:

As the microflow has the parameter Customer, and the data view has the object Photo, they are conflicting and resulting into an error.

The best way to fix this error is to either change the microflow to accept Photo or put the button in a data container for a different entity.

Input Widget Consistency Errors

The most common errors for input elements, their causes, and ways to fix them are described in the following sub-sections. For more information on input elements, see Input Elements.

Error Code: CE0544

CE0544 error message: This widget can only function inside a data container. Move it into a data view, list view or template grid.

You will get CE0544 if you have added an input widget to a page but it is not inside a data container. Input elements need to refer to an attribute of a specific entity type and entities are only available via data containers.

To fix CE0544, place this widget into a data container: a data view, list view, or template grid.

Error Code: CE0545

CE0545 error message: Select an attribute for this {widget name}.

You will get CE0545 if you have added an input widget and it is inside a data container, but an attribute is not selected for it.

To fix CE0545, do one of the following:

• Right-click the widget, click Select Attribute in the drop-down list, and set an attribute.
• Or open widget’s properties > the Data source section, and set an attribute in the Attribute (path) field.

Incorrect Multiplicity for a Reference Selector

Error message: Association {Name} must be a reference (not a reference set).

You will get this error message if you have added a reference selector and then you changed the association from reference type to reference set (from one-to-many or one-to-one to many-to-many).

A reference selector is a widget that is used to display and edit one-to-many or one-to-one associations. For more information on the widget, see Reference Selector.

For example, you have several employees who are associated with one city where they work. This is a one-to-many association: multiple Employees objects are associated with one City object. Associations that refer to a single object in this manner are references, as opposed to reference sets, in which multiple objects can refer to multiple other objects. In a reference, the “single object” side of the association is always the association’s owner. For more information on associations and their types, see Associations.

To fix this error, do the following:

1. Open your domain model and double-click the association that you are using for the reference selector.

2. In Properties of Association dialog box, change Multiplicity to one-to-many (in our example, multiple ‘Employee’ objects are associated with one ‘City’ objects).

   

3. Click OK to save changes.

You have changed the association multiplicity and fixed the error.

Incorrect Multiplicity for a Reference Set Selector and an Input Reference Set Selector

Error messages:

• Association {Name} must be a reference set (not a reference) – for an input reference set selector
• The reference set selector expects an association of type reference set that starts in the data view entity – for a reference set selector

You will get the above error messages if you have added an input reference set selector and then you changed the association from reference set type to reference (from many-to-many to one-to-many or one-to-one).

Reference set selector and input set selector are widgets that are used to display and edit many-to-many associations. For more information on these widgets, see Reference Set Selector and Input Reference Set Selector.

For example, you have several employees who can visit customers in different cities during the week. Thus, many employees are associated with many cities, this is a many-to-many association between an Employee entity and a City entity (multiple employees are associated with multiple cities). Associations that refer to multiple objects in this manner are reference set. For more information on associations and their types, see Associations.

To fix the errors, do the following:

1. Open your domain model and double-click the association that you are using for the reference set selector or the input reference set selector and do the following:
   

2. In Properties of Association dialog box, change Multiplicity to many-to-many (in our example, multiple ‘Employee’ objects are associated with multiple ‘City’ objects).

   

3. Click OK to save changes.

You have changed the association multiplicity and fixed the errors.

Images, Videos and Files Consistency Errors

Images, videos and files should be placed in a data container, otherwise you will get consistency errors. Another way to fix consistency errors is to place these widgets in a snippet and configure the snippet. For more information on images, videos, and files, see Images, Videos, and Files.

Image Widget Consistency Errors

A consistency error for an image widget is described in the table below:

On Click Event Consistency Errors

You can specify an On click event for different widgets, for example, for buttons or images.

The most common consistency errors are connected with not configuring the on click event.

To fix the consistency errors, finish configuring the on click event (for example, for an on click event Show a page, select a particular page that should open), or change the on click event.

Icon Collection Consistency Errors

Icon collections have configurable class names, icon prefixes, and icon names. These properties are used to generate the CSS code for your pages. You can come across the following consistency errors that prevent you from generating invalid CSS:

Read More

• Pages