Datasets
Datasets prepare form data for charts. You can choose a primary form, join related forms, add computed fields, and organize fields as dimensions or measures.
Create A Dataset
- Click Create dataset
- Enter a Name
- Add a Description when needed
- Click Create
After creation, double-click the dataset row to open the configuration page.
Configuration Page
The top bar provides:
| Action | Description |
|---|---|
| Back | Leaves the configuration page. Unsaved changes require confirmation |
| Save | Saves the current configuration. It is disabled when there are no changes |
| Delete | Deletes the current dataset. The system confirms first and checks whether the dataset is used by charts. If it is in use, continuing deletion also deletes charts that use this dataset |
The left side contains two areas:
| Area | Purpose |
|---|---|
| Dataset Properties | Edit the name, description, source type, primary form, and joined data |
| Fields And Metadata | Manage field names, dimensions/measures, aggregation, and visibility |
Choose The Primary Form
- Select Dataset Properties
- In Data, choose the primary form
- The system loads fields from the selected form
- Click preview to check the primary form data
The primary form is the base of the dataset. Chart results usually start from these records.
Changing the primary form clears joined data and computed fields, so configure them again after switching forms.
Add Joined Data
Use joined data when one analysis needs fields from multiple forms.
- Choose a primary form first
- Click the Join Data icon
- Select the left source
- Choose the join type
- Select the form to join
- Configure conditions such as
Customer = Record ID - When all conditions are complete, click preview to check the result
| Setting | Description |
|---|---|
| Left Source | The primary form or a previously joined form |
| Join Type | Determines which records are kept |
| Joined Form | The form added to the dataset |
| Join Condition | Uses left field = right field to match two forms |
Join Types
| Type | Kept Records | Use When |
|---|---|---|
| Left Join | Keeps all records from the left source. Right fields are empty when there is no match | The analysis should remain based on the primary records |
| Inner Join | Keeps only records that match on both sides | You only want records with a valid relationship |
| Right Join | Keeps all records from the joined form. Left fields are empty when there is no match | The joined form should drive the analysis |
| Full Join | Keeps records from both sides. Missing matches leave the other side empty | You need reconciliation or missing-relationship checks |
Left join is usually the best starting point when the chart should stay based on the primary form.
Join Conditions
Join conditions tell the system how two forms match.
| Left Field | Right Field | Meaning |
|---|---|---|
| Customer | Record ID | A customer field on the current form matches a customer record |
| Order No | Order No | Both forms use the same business number |
| Record ID | Order | The joined form has an order reference pointing to the left record |
Multiple conditions are combined together. A record must match every condition to be joined.
When fields already contain relationship settings, the system may fill the condition automatically after you choose the joined form. Use preview to confirm the result.
Add Computed Fields
Use computed fields when source fields do not directly provide the analysis value you need.
- In Dataset Properties, click Custom Column
- Enter the field name
- Choose the data type
- Choose the value source
- Configure the expression or script
- Save the computed field
Computed fields become new dataset fields. You can later configure them as dimensions or measures in Fields And Metadata.
| Setting | Description |
|---|---|
| Field Name | Display name used in charts |
| Data Type | Result type, such as number, string, date, datetime, or boolean |
| Value Source | Whether the value is calculated by an expression or written by a chart binding script |
Value Source
Value Source is a dropdown that controls how the computed field gets its value.
The dropdown options are:
- Expression: Calculates directly from primary-form and joined-form fields. Use it for fixed rules such as amount, duration, or status logic. Preview can show the computed value
- Studio Script: Defines the field in the dataset, then lets a chart binding script write the value during chart query. Use it for Studio logic, complex rules, or external calculation results
Use An Expression
After selecting Expression, insert fields from the current dataset and combine them with functions or operators.
| Scenario | Example |
|---|---|
| Amount calculation | Actual Amount = Order Amount - Discount |
| Time calculation | Handling Time = Completed At - Created At |
| Status judgment | Overdue = Due Date is earlier than today |
Expressions are best for values that can be derived from the current row. Use data preview to check the result.
Use A Studio Script
After selecting Studio Script, the dataset stores a script-backed computed field. The dataset preview does not calculate this value directly. Instead, a chart Binding Script writes the value when the chart queries data.
After saving the dataset, configure a chart binding script to write returned values into this computed field. See Charts - Binding Script.
Studio-script computed fields are useful for:
| Scenario | Description |
|---|---|
| External metrics | Fill a metric from an external service or script result |
| Complex rules | Use multi-step logic that is hard to maintain as an expression |
| Chart post-processing | Calculate target values, achievement rates, or forecasts from aggregated chart data |
Fields And Metadata
Select Fields And Metadata to manage dataset fields.
| Column | Description |
|---|---|
| Source Field | The source form, original field name, and API Name |
| Name | Display name used in charts |
| Role | Whether the field is a dimension or measure |
| Aggregation | How a measure is calculated |
| Status | Whether the field is enabled in the dataset |
Dimensions And Measures
| Role | Description | Examples |
|---|---|---|
| Dimension | Used for grouping, categories, and filters | Customer Type, City, Owner, Created Month |
| Measure | Used for numeric results | Order Amount, Order Count, Handling Time |
Changing the role updates the default aggregation.
Aggregation
| Aggregation | Description | Common Use |
|---|---|---|
| Sum | Adds numeric values | Order Amount, Payment Amount |
| Average | Calculates the average | Average Handling Time, Average Score |
| Count | Counts records | Order Count, Ticket Count |
| Distinct Count | Counts unique values | Customer Count, Owner Count |
| Max | Uses the largest value | Highest Amount, Longest Duration |
| Min | Uses the smallest value | Lowest Amount, Shortest Duration |
Number fields can use all aggregation types. Non-number fields usually support count and distinct count.
Field Status
| Status | Description |
|---|---|
| Visible | The field can be used in charts |
| Hidden | The field stays in the dataset but is hidden from normal chart configuration |
If a source form field is deleted or changed, the dataset may show invalid fields. Invalid fields can be remapped to compatible fields or deleted in bulk.
Preview Data
Preview data after configuring the primary form, joined data, or computed fields.
Check that:
- primary form records are correct
- joined records match as expected
- the join type does not unexpectedly add or remove records
- computed field results are correct
- field names are clear for business users
Click Save after confirming the result.