--- title: "Conditional Configuration Dataset" slug: "conditional-configuration-dataset" updated: 2026-05-19T13:28:58Z published: 2026-05-19T13:28:58Z canonical: "skthelp.syniti.com/conditional-configuration-dataset" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Conditional Configuration Dataset ## Overview A conditional configuration dataset (CCD) is equivalent to a Data Control View in the legacy Construct. CCD’s view is created in SQL Server and define record-level control based on what is known about the data on a Grid or Properties Card container. CCD contains conditional information that individually set the control status of each record in a column. For example, a CCD could be used to determine if a record can be edited or deleted, or if records are hidden based on the value of the record. Configuring a CCD involves the following steps: 1. Create the CCD view in SQL Server. 2. Run a scan to import the view and create it as a Dataset. 3. Register the CCD in a WebApp’s Grid or Properties Card container. ## Create the CCD View CCD views are created in a working database (PostgreSQL or SQL Server). Use the following guidelines to create a CCD view: - Use the naming convention web*Ccd, where * contains the name of the table registered to the gird or properties card container. - The view should include all key and criteria columns used on the container to control. - Include all column names for the technical names of the columns on the container that contain the control status values. - 0 = Disable - 1 = Enable - 2 = Hide - Prefix the column containing the control status with "ccdCtl" when assigning a control status to a key column. ## Run a Scan and Create CCD 1. Access the datastore in the Syniti Knowledge Platform (SKP) Catalog module associated with the database where the CCD view was created. 2. [Scan](/v1/docs/scan-a-system) the datastore to ingest metadata into the SKP. 3. [Create a dataset](/v1/docs/datasets) using the same view name. 4. Set the **Affected Table** field. ## Register CCD in a Container 1. On the Cloud Construct’s home page, edit the required WebApp. The WebApp configuration page is displayed. 2. Access **Pages** **> Your Page > Grid or Properties Card** in the Tree Navigation panel. The Details panel is updated with the Grid or Properties Card fields. 3. Access the **Data** section and select the newly created dataset from the Conditional Configuration Dataset list. 4. Click **Save & Preview WebApp** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-950XFTN7.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A45%3A23Z&se=2026-11-17T20%3A45%3A23Z&sr=b&sp=r&sig=uFf9XzKSnX5EfyaGOy2AL3CtnQs2uq36EkXLVhlUWUk%3D) to preview WebApp changes. 5. Click **Save WebApp** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-PQGG609G.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A45%3A23Z&se=2026-11-17T20%3A45%3A23Z&sr=b&sp=r&sig=nXraxeIHUyKIYDTGOnhW9RPqfQNeLV9yWyCAp%2BjWI9k%3D) . > [!NOTE] > Note > > - The **Update CCD** button opens a dialog box that allows you to rescan the dataset and add any newly available fields from the underlying view to the CCD used in this container. > - Specify the dataset classification. > - If the scan errors out, access the associated Datastore’s scan logs in the SKP Catalog module to troubleshoot the error. > - Be sure the primary dataset for the Container has the Affected Table configured and that table has a primary key. The CCD view must have a column that matches one or more of the table’s primary key columns. ## Example Below is an example of a view that creates a CCD in the SKP. The `Customer` table, which has a primary key of `CustomerID`, requires specific controls on the customer management page. - The `Approved` and `AlreadyinERP` bit fields on each record are used to control whether the record can be edited or deleted. - The `CustomerID` key field remains editable as long as the record has not yet been added to the target ERP system. - The `Address`, `ContactName`, and `ContactTitle` fields use special controls for certain account categories. - Finally, the Approved button is disabled once a record has already been approved. ### View DDL ```sql SELECT        CustomerID, --Primary Key field CASE WHEN AlreadyInERP = 1 THEN 0 WHEN Approved = 1 THEN 0 ELSE 1 END AS ccdDelete, --Disables Delete for Records Already in ERP CASE WHEN Approved = 1 THEN 0 ELSE 1 END AS ccdEdit,  --Disables Edit for Records Approved CASE WHEN AlreadyInERP = 1 THEN 0 ELSE 1 END AS ccdCtlCustomerID, --Cannot change Customer ID Key value CASE WHEN AccountCat = 'SP' THEN 2 WHEN AccountCat = '02' THEN 0 ELSE 1 END AS Address, --Hides or Disables Address for special account category. CASE WHEN AccountCat = 'SP' THEN 2 WHEN AccountCat = '02' THEN 0 ELSE 1 END AS ContactName, CASE WHEN AccountCat = 'SP' THEN 2 WHEN AccountCat = '02' THEN 0 ELSE 1 END AS ContactTitle, CASE WHEN Approved = 0 THEN 1 ELSE 0 END AS Approve  --Disables Approval button for Records Approved FROM           dbo.Customers ``` ### Rendered Grid Container ![Table displaying customer change approvals with various statuses and company details.](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/Customer Change Approval.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A45%3A23Z&se=2026-11-17T20%3A45%3A23Z&sr=b&sp=r&sig=%2FwX%2Biidz%2BcyrAF6Xgq304dmpqkTcqQo%2FlcDMIi5y75E%3D)