Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This page outlines Step 1 of Deploying CinchyDXD: Building the Data Experience
Remember that you must create all objects in one source environment (ex: DEV). From there, DXD will be used to push them into others (ex: SIT, UAT, Production).
Create your data experience (DX) in a virtual data network.
Log in to Cinchy: URL: <Cinchy source URL> User ID: <source user id> Password: <source password>
From the Homepage, select Create
Select Table > From Scratch
Create the table with the following properties (Image 1).
Click Columns in the left hand navigation to create the columns for the table
Click the “Click Here to Add” a column tab to add a column
8. Click the Save button to save your table
In your newly created table, enter the following sample data (Image 2).
Create a simple query that pulls information from the Currency Exchange Rate table that will allow a simple currency exchange calculation.
From the Homepage, select Create.
Select Query.
In the query builder locate the Currency Exchange Rate table and drag it to the “FROM” line (Image 3).
You will find the Currency Exchange Rate table in the “Sandbox” domain. To expand the “Sandbox” domain, click on the gray arrow (or double click)
In the “SELECT” line drag and drop the “Rate” column and enter in the following (Image 4):
SELECT [Rate] * @Amount AS 'Converted Amount'
You will find the Rate column by expanding the Currency Exchange Rate table, similarly to expanding the “Sandbox” domain
Enter in the following for the WHERE clause (Image 5):
WHERE [Deleted] IS NULL
AND [Currency 1] = @Currency_1
AND [Currency 2] = @Currency_2
Click the Execute (or play) icon to run the query (Image 6):
Test the query by entering in the following and clicking the submit button (Image 7):
@Amount: 100
@Currency_1: CAD
@Currency_2: USD
Save the Query by clicking on the Info tab (Left Navigation)\
Enter in the following details for the query (Image 8):
Click the Save button (Image 9).
Column Details | Values |
---|---|
Currency 1 | Currency 2 | Rate |
---|---|---|
Query Details | Values |
---|---|
Column 1
Column Name: Currency 1
Data Type: Text
Advanced Settings:
Select Mandatory
Leave all other defaults
Column 2
Column Name: Currency 2
Data Type: Text
Advanced Settings:
Select Mandatory
Leave all other defaults
Column 3
Column Name: Rate
Data Type: Number
Advanced Settings:
Set Decimal Places to 4
Select Mandatory
Leave all other defaults
CAD
USD
0.71
USD
CAD
1.40
Query Name
Currency Converter
Icon + Colour
Choose your own icon
Return
Query Results (Approved Data Only)
Domain
Sandbox
API Result Format
JSON
Description
This query is a test query for building and deploying a data experience for currency conversion
This page guides you through the Cinchy Data Experience Deployment Utility.
CinchyDXD is a downloadable utility used to move Data Experiences (DX) from one environment to another. This includes any and all objects and components that have been built for, or are required in, support of the Data Experience.
The following sections in this document will outline the basics of how to build, export**,** and install a DX’s.
Items of note moving forward in this document:
Source Environment is the environment in which the DX is built.
All objects need to be created in one source environment (ex: DEV). From there, DXD will be used to push them into others (ex: SIT, UAT, Production).
Target Environment is the environment in which the DX will be installed.
The example DX is a simple Currency Converter DX that consists of
One (1) table
One (1) query
This example doesn't include the following:
NO applets
NO integrated clients
NO Data Sync Configurations
NO Reference Data
NO Models
NO Groups
NO System Colours
NO Formatting Groups
NO Literal Groups
Future iterations of this document will add to this example's complexity level.
The general steps to deploying the CinchyDXD Utility are as follows:
This page outlines Step 5 of Deploying CinchyDXD: Repackaging the Data Experience
After you have made any applicable changes to your DX, you must re-export the package out of your source environment.
If you have added or removed any of the following while updating your DX, you will need to update the Data Experience Definition table:
Name
Tables
Views
Integrated Clients
Data Sync Configurations
Listener Configurations
Secrets
Reference Data
User Defined Functions
Models
Groups
System Colours
Saved Queries
Pre-Install Scripts
Post-Install Scripts
Applets
Literal Groups
Webhooks
Builders
Builder Groups
Sync GUID
If you have added or removed any of the following while updating your DX, you will need to update the Data Experience Reference Data table:
Name
Ordinal
Filter
New Records
Changed Records
Dropped Records
Table
Sync Key
Expiration Timestamp Field
Sync GUID
Using PowerShell you will now export the Data Experience you have defined within Cinchy.
Launch PowerShell and navigate to your CinchyDXD folder
You can launch PowerShell right from your file explorer window in the CinchyDXD file, saving you an extra step of navigating to the CinchyDXD folder manually in PowerShell.
2. In the PowerShell window type in cin
and hit tab on your keyboard
3. In the PowerShell command line next to .\CinchyDXD.ps1 type in export
4. Hit Enter on your keyboard
If you don't remember the mandatory parameters, you can click the enter on your keyboard after typing in .\CinchyDXD.ps1 export, PowerShell will provide you with the required and optional components to export the data experience.
5. You must now enter your mandatory export parameters.
The parameters executed in PowerShell can exist on one line in PowerShell, but for legibility (below) the parameters are on separate lines. If you are putting your parameters on separate lines you will be required to have backticks quote ` for the parameters to execute
You will need to update your version number
Sample:
.\CinchyDXD.ps1 export `
-s "<source Cinchy url>" `
-u "<source user id>" `
-p "<source password>" `
-c "C:\Cinchy CLI v4.0.2" `
-d "C:\CLI Output Logs" `
-g "8C4D08A1-C0ED-4FFC-A695-BBED068507E9" `
-v "2.0.0" `
-o "C:\CinchyDXD_Output" `
\
Enter the export parameters into the PowerShell window (Image 1).
Hit Enter on your keyboard to run the export command
PowerShell will begin to process the export. Once the export is complete, PowerShell will provide you with an export complete message (Image 2).
Ensure that the DXD Export Folder is populated (Image 3).
Ensure that the Data Experience Release table is populated in the source environment (Image 4).
Ensure that the Data Experience Release Artifacts table is populated in the source environment (Image 5).
Table Details
Values
Table Name
Currency Exchange Rate
Icon + Colour
Choose your own icon
Domain
Sandbox (if the domain doesn't exist, create it)
To create a domain on the fly:
Enter domain name in Domain field
Hit enter on keyboard
On the Confirm Domain window, click Yes
Description
This table is a test table for building and deploying a data experience for currency conversion
This page outlines Step 3 of Deploying CinchyDXD: Installing the Data Experience
The install of a Data Experience is executed in a different environment than that of the export. Please ensure that before moving forward with the following instructions you have an environment to install the data experience into. The install of a data experience MUST be done in the same version. Your source and target environment version MUST be the same (For example, Source Version = 4.11 | Target Version = 4.11).
Below are the details that will be required for the installation environment:
Source: <Cinchy target url>
UserID: <target user id>
Password: <target password>
Using PowerShell you will now install the Data Experience you have exported out of Cinchy.
Open the File Explorer and navigate to your DX exported folder (Image 1).
In the folder path URL of the exported data experience type in PowerShell to launch PowerShell for that path (Image 2).
Hit Enter on your keyboard, the PowerShell window will appear (Image 3).
In the PowerShell window, type in cin
and hit tab on your keyboard (Image 4).
In the PowerShell command line, type install (Image 5).
Hit Enter on your keyboard (Image 6).
The PowerShell window will provide you with the required and optional components to install the DX.
You must now set up your mandatory install parameters
The parameters executed in PowerShell can exist on one line in PowerShell, but for legibility (below) the parameters are on separate lines. If you are putting your parameters on separate lines you will be required to have backticks quote ` for the parameters to execute
Sample:
.\CinchyDXD.ps1 install`
-s "<target Cinchy url>" `
-u "<target user id>" `
-p "<target password>" `
-c "C:\Cinchy CLI v4.0.2" `
-d "C:\CLI Output Logs" `
Be sure that the user(s) and group(s) required to install a DX are existing in your target environment. If they don't exist, PowerShell will generate an error message when you attempt to install the DX.
Enter the install parameters into the PowerShell window (Image 7).
Hit Enter on your keyboard to run the install command. Once the Data Experience has been installed you will get a message in PowerShell that the install was completed (Image 8).
Ensure that the Models Table is populated in the target environment with the model that was installed (Image 9).
Ensure that the Currency Exchange Rate table exist in the target environment (Image 10).
Ensure that the Currency Converter query exist in the target environment (Image 11).
Ensure that the Data Experience Definitions table is populated with the DX parameters that were set up in the source environment (Image 12).
Ensure that the Data Experience Releases table in the target environment is populated (Image 13).
This page outlines Step 4 of Deploying CinchyDXD: Updating the Data Experience
The Data Experience has required updates you must create in your source environment. You don't want to have to repeat the updates in both the source and target environments. The upcoming section will show how to update the data experience in the source environment so that you can then re-package and reinstall in the target environment.
Log back into your source environment using the following: URL: <Cinchy source url> User ID: <source user id> Password: <source password>
Make the following changes to the Currency Exchange Rate table:
Column Details | Values |
---|---|
3. Save your changes before leaving the table.
Update the Currency Converter query to reflect column name changes that were made in the Table Updates section above (Image 1).
Be sure to update the @Currency_1 and @Currency_2 labels to better reflect the input fields
Test the query to validate that it's still functioning (Image 2 and 3).
Save your query.
This page outlines Step 6 of Deploying CinchyDXD: Reinstalling the Data Experience
Using PowerShell, you must now install the Data Experience you have exported out of Cinchy.
Open File Explorer and navigate to your exported folder (Image 1).
In the folder path URL of the exported data experience, type in PowerShell to launch PowerShell for that path.
Hit Enter on your keyboard (Image 2).
In the PowerShell window, type cin
and hit Tab on your keyboard. Type install (Image 3).
Enter the install parameters into the PowerShell window:
The parameters executed in PowerShell can exist on one line in PowerShell, but for legibility (below) the parameters have been put on separate lines. If you are putting your parameters on separate lines you will be required to have backticks quote ` for the parameters to execute
Sample (Image 4):
.\CinchyDXD.ps1 install
-s "<taget Cinchy url>" `
-u "<target user id>" `
-p "<target password>" `
-c "C:\Cinchy CLI v4.0.2" `
-d "C:\CLI Output Logs" `
Hit Enter on your keyboard to run the install command. Once the Data Experience has been installed you will get a message in PowerShell that the install was completed (Image 5).
Ensure that the Models Table is populated in the target environment with the model that was installed (Image 6).
Ensure that the Currency Exchange Rate table exists in the target environment with the new column names (Image 7).
Ensure that the Currency Converter query exists in the target environment with the new column names and labels (Image 8).
Ensure that the Data Experience Definitions table hasn't changed, unless you have added or removed column details within this table (Image 9).
Ensure that the Data Experience Releases table in the target environment is populated with the new release version number from the install (For example: 2.0.0) (Image 10).
This page outlines Step 2 of Deploying CinchyDXD: Packaging the Data Experience
The CinchyDXD utility takes all the components (tables, queries, views, formatting rules) of a DX and package them up so they can be moved from one environment to another.
Remember that all objects need to be created in one source environment (ex: DEV). From there, DXD will be used to push them into others (ex: SIT, UAT, Production).
The CinchyDXD utility is only required (made accessible) for the environment that's packing up the data experience. It's not required for the destination (or target) environment.
For CinchyDXD to work, you must have CinchyCLI installed. For further installation instructions please refer to CLI () documentation
To access the Data Experience Deployment utility please contact Cinchy support (support@cinchy.com).
To download the Utility:
Login to Cinchy
Navigate to the Releases Table
Select the Experience Deployment Utility View
Locate and download the utility (Cinchy DXD v1.7.0.zip)
The CinchyDXD utility is only upwards compatible with Cinchy version 4.6+
Unzip the utility and place the folder at any location on a computer that also has CinchyCLI installed
Create a new folder in the same directory that will hold all of the DX exports generated (CinchyDXD*Output) *(Image 1)._
This folder will then hold all your deployment packages.
Launch a PowerShell console window
From the console, navigate to the CinchyDXD directory (Image 2 and 3).
From within your file explorer window, type “PowerShell” into the file path. It will launch a PowerShell window already at the folder path
PowerShell requires an initial setup when using CinchyDXD.
From your PowerShell window type cin
Hit Tab on your keyboard (Image 4).
Hit Enter on your keyboard (Image 5).
You will get an error message (above) that CinchyDXD.ps1 can't be loaded because the running script is disabled
.
To resolve this error:
From your start menu, search for PowerShell and select Run as Administrator (Image 6).
When prompted if you want to allow this app to make changes on your device, select Yes.
In your PowerShell Administrator window enter Set-ExecutionPolicy RemoteSigned (Image 7).
Hit Enter on your keyboard (Image 8).
When prompted with the Execution Policy Changes, enter A for “Yes to All”
Close the PowerShell Administrator window
Navigate back to your PowerShell window for the CinchDXD window
From your PowerShell window type cin
Hit Tab and then Enter on your keyboard (Image 9).
The basic CinchyDXD instructions will be displayed. You will be able to execute commands such as exporting and installing a Data Experience.
Cinchy uses four tables for packing up and deploying a Data Experience (Image 10).
The Data Experience is defined and packed in what will be referred to moving forward as the Source Environment. Where the environment that the Data Experience will be deployed to will be referenced to as the Target Environment.
Data Experience Definition Table: Where the data experience is defined (tables, queries, views, formatting rules, UDF’s etc.)
Data Experience Reference Data Table: Where we define any data that needs to move with the Data Experience for the experience to work (lookup values, static values that may need to exist in tables - it typically would not be the physical data itself)
Data Experience Releases Table: Once a Data Experience is exported, an entry is created in this table for the export containing:
Version Number
Release Binary is the location where you can archive/backup your release history in Cinchy Please Note: if you have your own release management system, you do have the option to opt out of archiving the releases in Cinchy and check the release into your own source control
Release Name
Data Experience
Data Experience Release Artifact Table: Stores all of the files that are part of the Data Experience package as individual records along with all of the binary for each record
When setting up a Data Experience definition, you will need one definition for each Data Experience you wish to package and deploy to a given number of Target Environments.
Locate and open the Data Experience Definitions table (Image 11).
2. Complete the following (Image 12):
If you make changes to the DX in the future, you aren't required to build a new Data Experience Definition in this table, you will update the existing definition. If you need to review what the definition looked like historically, you can view it via the Collaboration log.
When setting up a Data Experience Reference Data definition, you will need one (1) definition for each Reference Data table you wish to package and deploy with your Data Experience to the Target Environment.
This table set up is similar to setting up a CLI.
Locate and open the Data Experience Reference Data table (Image 13).
Based on the configuration set up in this table, Cinchy will export the data and create CSV and CLI files.
This example doesn't have Reference Data as part of the Data Experience.
Using PowerShell you will now export the Data Experience you have defined within Cinchy.
Launch PowerShell and navigate to your CinchyDXD folder (Image 14).
Reminder: you can launch PowerShell right from your file explorer window in the CinchyDXD folder by entering in the folder path “PowerShell” and hitting enter on your keyboard. Saving you an extra step of navigating to the CinchyDXD folder manually in PowerShell (Image 15).
In the PowerShell window type in cin
and hit Tab on your keyboard (Image 16).
Hit Enter on your keyboard, you will see a list of commands that are available to execute (Image 17).
In the PowerShell command line hit your “up” arrow key to bring back the last command and type export next to it (Image 18).
Hit Enter on your keyboard (Image 19).
The PowerShell window will provide you with the required and optional components to export the data experience.
You must now set up any mandatory export parameters
The parameters executed in PowerShell can exist on one line in PowerShell, however for legibility (below) the parameters have been put on separate lines. If you are putting your parameters on separate lines you will be required to have backticks quote ` for the parameters to execute.
Please ensure that you are using the sample below as a sample. You will be required to provide values that correspond to:
the URL of the source environment
the User ID for the user who is performing the export
the Password for the user who is performing the export
your folder path for where CLI is stored
your folder path for where the CLI output files are written to
the GUID for the Data Experience that's generated in the Data Experience Definition table
your own version naming convention
your folder path for where your CinchyDXD output files are written to
Sample: .\CinchyDXD.ps1 export `
-s "<cinchy source url>" `
-u "<source user id>" `
-p "<source passsword>" `
-c "C:\Cinchy CLI v4.0.2" `
-d "C:\CLI Output Logs" `
-g "8C4D08A1-C0ED-4FFC-A695-BBED068507E9" `
-v "1.0.0" `
-o "C:\CinchyDXD_Output" `
\
Enter the export parameters into the PowerShell window (Image 20).
Hit Enter on your keyboard to run the export command.
PowerShell will begin to process the export. Once the export is complete, PowerShell will provide you with an export complete message (Image 21).
Ensure that the DXD Export Folder is populated (Image 22).
2. Ensure that the Data Experience Release table is populated in the source environment (Image 23).
3. Ensure that the Data Experience Release Artifacts table is populated in the source environment (Image 24).
Column | Definition |
---|
Column | Value |
---|
Column | Definition |
---|
GUID | This value is calculated, please note this value will be required as one of your export parameters in PowerShell |
Name | This is the Name of your Data Experience |
Tables | Select all tables that are part of the Data Experience |
Views | Select all views (in the data browser) that are a part of the Data Experience |
Integrated Clients | Select any integrated clients (For example: Tableau, PowerBI, custom integrations) that are part of the Data Experience |
Data Sync Configurations | Select any data syncs (CLI’s experience needs to work) that are part of the Data Experience |
Listener Configurations | Select any Listener Config rows that refer to a Data Sync Configuration which is a part of the Data Experience |
Reference Data | Select any reference data that's part of the Data Experience. Please note that the setup of the reference data is done in the table called Data Experience Reference Data (see step 2 below for setup details) |
Secrets | Select any Secrets you'd like to include that are used Data Sync Configurations or Listener Configs which are a part of this Data Experience. |
Webhooks | Select any Webhooks that are a part of this data experience |
User Defined Functions | Select any user defined functions (For example: validate phone, validate email) that are part of the Data Experience |
Models | Select any custom models that override columns or tables in your Data Experience, if there are none - leave blank |
Groups | Select any groups that are part of the Data Experience (when moving groups, it will also move all table access [design] controls) |
System Colours | Select a system colour (if defined) for the Data Experience |
Saved Queries | Select any queries that are part of the Data Experience |
Applets | Select any applets that are part of the Data Experience |
Pre-install Scripts | Select any Pre-install Scripts (Saved Queries) that should run before the installation of this Data Experience. |
Post-install Scripts | Select any Post-install Scripts (Saved Queries) that should run after to the installation of this Data Experience. A common use-case is to rectify data that may be different between environments. |
Formatting Rules | Select any formatting rules that are part of the Data Experience |
Literal Groups | Select any literals associated to the Data Experience (For example: key values with English and French definitions) |
Builders | Select the builder(s) who have permission to export the Data Experience |
Builder Groups | Select the builder group(s) that have permission to export the Data Experience Note: Best Practice is to use a Group over a User. Users within groups can fluctuate, where the Group (or Role) will remain. This will require less maintenance moving forward |
Sync GUID | Leave this column blank |
Name | Currency Converter |
Tables | Currency Exchange Rate (Sandbox) |
Saved Queries | Currency Converter |
Builder Groups | Currency Converters |
Name | This is the Name of your Reference Data Table, note this name can be anything and doesn't have to replicate the actual table name |
Ordinal | The ordinal number assigned will identify the order in which the data is loaded and required based on dependencies within the data experience. For example if you have tables that have hierarchies in them, you will need to load the parent records first and then load your child records which would then resolve any links in the table. |
Filter | This is where a WHERE clause would be required. For example, if you have a table that has hierarchies, you would require two rows within the Data Experience Reference Data table. One to load the parent data and one to load the children data. In the parent record a filter WHERE clause would be needed to filter all parent records. In the second record in the filter column a WHERE clause in another in the second record that would be needed to filter the children records. |
New Records | Identify the behaviour of a new record (INSERT, UPDATE, DELETE, IGNORE) |
Change Records | Identify the behaviour of a changed record (INSERT, UPDATE, DELETE, IGNORE) |
Dropped Records | Identify the behaviour of a dropped record (INSERT, UPDATE, DELETE, IGNORE) |
Table | Identify the table that you are exporting data from |
Sync Key | Required (need definition) |
Expiration Timestamp Field | If Dropped Records is set to “Expire” then a timestamp column is required |
Column 1
Current Column Name Value = Currency 1
New Column NameValue = From Currency
All other settings remain the same
Column 2
Current Column Name Value = Currency 2
New Column NameValue = To Currency
All other settings remain the same