Methodology Updates in Construct Preview

Prev Next

Overview

With the release of Construct Preview,  we’re introducing significant changes to how you reference and manage data within the application. A major shift is the adoption of the Syniti Knowledge Platform’s (SKP) Dataset model, which serves as the foundation for all data interactions in Construct Preview.

In this model, Datasets will represent references to either database tables or views instead of direct Data Source connections like in the prior version of Construct. This change improves flexibility and consistency in how you access and update data. You will now create datasets from the underlying database structure—either from a table or a view.

Key Points to Remember

  • For the most part, existing methodologies and naming conventions can remain unchanged in Construct Preview.

  • Tables, filters, and other familiar components can still use the same names and logic structures you are accustomed to.

  • Construct Preview uses a concept of containers to define a page’s content and layout.

  • Note that the prior version of Construct has already switched to Datastores, and Construct Preview can use that same Datastore.

  • Tables and list views must now be created as Datasets within SKP.

    Note

    When using a view, you must specify the name of the affected table in the dataset details to ensure that updates are correctly applied to the underlying data.

  • Validations and procedures will continue to work as they have before and do not need to be converted into datasets. This allows you to maintain your current workflows with minimal disruption.

Construct Preview Dataset Naming Conventions

Data

Naming Convention in Construct

Naming Convention in Construct Preview

Table Filter

tt*

The same table name can be registered as Dataset.

Horizontal Filter

web*Hor

You can create a dataset from the fields in a single view. Be sure to set the affected table for the dataset to the table that holds the data you want to manage on the page.

Vertical Filter

web*Ver

Use the same name, but the data must be a Table dataset.

List Filter

web*List

The same view name can be registered as Dataset.

Procedure Filter

web*

The same view name can be registered as Dataset.

Validation Filter

web*Val

The same view name can be registered as Dataset.

Event Parameter Filter

web*Evt

Not supported yet.

Defaults Filter

web*Def

Not supported yet.

User Control Filter

web*Ucv

Not supported yet.

Page Control Filter

web*Pcv

Not supported yet.

Data Control Filter

web*Dcv

web*Ccd. Refer to Conditional Configuration Dataset for more information.

web*Dcv is also supported for backward compatibility.

List Control Filter

web*Lcv

Not supported yet.

Parameter Filter

web*PV

Not supported yet.

Toolbar Filter

web*Tbv

Not applicable. Replaced with Toolbar buttons.

Refer to Configure Toolbar Buttons for more information.

Tooltip Filter

web*Dtv

Not supported yet.

Construct Preview Component Naming Conventions

Use the naming conventions below for the components used in Construct Preview.

Component Type

Naming Convention

Examples

Container

con{pagelocation}

conUpperLeft, conTop, conBottom

Tab Container

tab*

tab1, tabOrders, tabOrderDetails

Grids

grd*

grdOrders, grdCustomers (in Plural)

Properties Card

crd*

crdOrder, crdCustomer (in Singular)

Charts

chrt*

chrtOrdersByMonth

Events

evt*

evtSendEmail

Construct Preview Page Component Comparisons

Old Component

Comparable Feature

Notes

Horizontal View

Grid

Presentation of Multiple Records in a Grid.

Vertical View

Property Card

Presents a single record of data. Construct Preview does not support fly-out functionality at this time.

Labels

Not supported yet

Collapsible sections in a vertical view.

Tabs

Tab Container

In the legacy Construct, a Tab was another way of segmenting a Vertical view of data. In Construct Preview, a Tab Container is a presentation-management container that can have one or more containers of any type.

Header Detail Page

Container

Use the FlowVertical layout option, then add Grid or Property Card containers for your Header and Detail components.

Multiple Detail Pages

Tab Container that contains multiple Grids or Property Cards.

In the legacy Construct, you created separate Dynamic pages that could be linked from the Header page. In Construct Preview, these are implemented as separate containers on the same page.

Reserved Word Updates

Refer to Reserved Words in Construct Preview for a complete list of reserved words available in Construct Preview.

Related Articles