Manage Data Sets

This section displays credited options available for a Data Set.

Use the Options context menu to manage an existing Data Set—edit, publish, version, share, and more.

Accessing the Data Sets Options

Navigation path: Data Center → Standard Connectors → Data Sets List → Vertical Ellipsis () → Options for a Data Set

1. Open Data Center > Standard Connectors > Data Sets.

2. Select a Data Connector.

   • The Data Sets tab lists all Data Sets created using that connector.

3. Locate your Data Set and click the Vertical Ellipsis () icon next to it.

4. The Options context menu appears for that Data Set.

5. Supported Options for a Data Set are:

   1. Create Widget- Redirects to create a Widget

   2. Create Data Form - Redirects to create a Data Form

   3. Create Data As API - Redirects to create a Data As API

   4. Create Data Preparation - Redirects to the Data Preparation module to prepare data.

   5. Pull From VCS - Pulls a version from the VCS

   6. Push to VCS - Pushes a new version to the VCS

   7. Publish - Publishes the Data Set

   8. Share - Redirects to the Manage Access window to share the Data Set

   9. Edit - Opens the Data Set form with editable fields to modify

   10. Delete - Removes the selected Data Set

Note: Please refer to the Create a Widget, Create a Data Form, Create a Data As API, and Data Preparation sections to get more details on it. The remaining Options for a Data Set are explained below.

Push to VCS (Data Sets)

Use Push to VCS to version a Data Set and store its latest snapshot in your Git-backed Version Control System. When teammates later Pull from VCS, they’ll see your Commit message alongside each version for quick context.

Prerequisites:

• You can access Data Center → Data Sets.

• The Data Set is saved, and you have permission to push versions.

• VCS/Git integration is configured for your environment.

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Push to VCS

Steps: Push a version of a Data Set to VCS

1. Open Data Center → Data Sets and locate the target Data Set.

2. Click the Push to VCS icon next to the Data Set. Result: The Push into Version Controlling System dialog opens.

3. Enter a Commit message.

   • This message is saved as the label for the version in the VCS.

   • Required: The Push button is enabled only after you enter a message.

4. Click Push.

• A confirmation message appears, and the current Data Set version is pushed to VCS.

What happens next

• The Data Set’s state (definition, query, metadata) is stored as a new version in Git.

• Teammates will see your Commit message when they pull from VCS, helping them choose the correct version.

Best practices

• Write clear, concise commit messages (e.g., “Add @region@ filter; fix JOIN to sales_fact”).

• Push after meaningful changes so the history remains useful.

• Pair pushes with Publish only after validation if downstream dashboards depend on the Data Set.

Troubleshooting

• Push button disabled: Enter a Commit message.

• Auth/repo errors: Verify VCS credentials and repository configuration with your admin.

• Unexpected content after pull: Ensure you pushed the intended Data Set and version; review commit messages to confirm.

Pull from VCS (Data Sets)

Retrieve a previously saved version of a Data Set from your Git-backed Version Control System.

Prerequisites:

• VCS/Git integration is configured.

• The Data Set has at least one version pushed to VCS.

• You have permission to pull from VCS.

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Pull from VCS

Steps: Pull a Data Set version

1. Go to Data Center → Data Sets and locate the target Data Set (one that has versions in VCS).

2. Click Pull from VCS (action icon).

   • The Pull from Version Controlling System dialog opens, listing versions with metadata:

     • Select: A Checkbox to choose a version.

     • Version: Version label (e.g., V1, V2, …).

     • Commit: Commit message (helps identify the change).

     • Commit time: Date & time the version was committed.

     • Committed By: User who pushed the version.

3. Check the box next to the version you want.

4. Click Pull.

   • A confirmation message appears once the selected version is pulled.

Note: The Pull button is enabled only after you select a version.

What changes after Pull

• The Data Set definition is replaced with the selected version (query, settings, and metadata from that commit).

• You can Validate to preview results, then Save and optionally Publish.

Best practices

• If you have unsaved local edits, Save or Save As before pulling to avoid losing work.

• Use the Commit message, time, and author to pick the correct version.

• After pulling, validate and test downstream assets (dashboards/APIs) before publishing.

Publishing a Data Set

Publish a Data Set to make it available for downstream use, such as inside the Designer module.

Prerequisites:

• You have permission to Publish Data Sets.

• The Data Set validates successfully (query runs and saves).

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Publish

Steps to Publish

1. Navigate to the Data Sets list for a standard connector.

2. Locate the target Data Set.

3. Open the Options context menu for the data set by using the Vertical Ellipsis icon.

4. Click the Publish option from the context menu.

5. The Publish Data Set dialog opens.

   1. Click Yes to confirm.

• A confirmation message appears, and the Data Set is published. In the list, a Publish indicator shows the Data Set’s published status.

Note: The Publish () icon appears beside a Data Set name once it has been published.

What Publishing Does

• Marks the Data Set as available to dependent modules (E.g., Dashboards).

• Keeps a clear Published status in the list for auditing and discovery.

Troubleshooting

• Publish icon disabled: Ensure you have publish rights and the Data Set is saved.

• Consumers don’t see updates: Republish after significant changes, and verify sharing/permissions.

• Validation errors: Fix query/connection issues and validate before publishing.

Sharing a Data Set

Share a Data Set with specific users or user groups, optionally exclude individuals, and revoke access when needed. Shared Data Sets appear in the recipient’s Data Sets list; available actions depend on the permissions you grant.

Prerequisites

• You can access Data Center → Data Sets.

• You have permission to share the target Data Set.

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Share

Share a Data Set (Users or User Groups)

1. Navigate to the Data Sets list for a standard connector.

2. Open the Options context menu by clicking the Vertical Ellipsis icon for the target Data Set

3. Click Share from the context menu.

4. The Manage Access dialog window appears for the selected Data Set.

5. In Grant Permissions, select the permission checkboxes (e.g., View & Edit).

6. Select recipients using the following tabs:

   • Users: search and check user(s). (Supports single or multiple users.)

   • User Groups: search and check group(s). (Supports single or multiple groups.)

7. Click Save.

• A success notification appears. The Data Set is added to the recipients’ Data Sets list with the granted privileges.

Exclude Users

Use Exclude User to block specific people—even if they belong to a group that has access.

1. In Manage Access for the Data Set, open the Exclude User tab.

   • Only users who are members of the granted group(s) are listed here.

2. Search and select the user(s) to exclude.

3. Click Save.

• The selected users move to Excluded Users and can’t access the Data Set.

Include a Previously Excluded User

1. Open the Manage Access window for the shared Data Set.

2. Go to the Excluded Users list.

3. Select the user → click Include User.

• A notification confirms restoration of privileges; the Excluded Users list updates.

Revoke Privilege(s)

Remove access for a user or group that was previously granted.

1. Open the Manage Access window.

2. In Granted Permissions, locate and select the user or user group.

3. Click Revoke Privileges.

• A notification confirms revocation; the Granted Permissions list updates.

Notes & Tips:

• The Action permissions available to a recipient depend on what you selected in Grant Permissions.

• Exclude User only lists users who belong to the granted group(s).

• You can share a Data Set with a single or multiple groups; the steps are the same as sharing with users.

• After any change (Share / Exclude / Include / Revoke), click Share/Save to apply.

• Prefer group-based sharing for scalable access; use Exclude User for exceptions.

• Use clear permission levels (e.g., View-only for consumers; Edit for data engineers).

• To audit who has access, review Granted Permissions and Excluded Users in Manage Access.

Editing a Data Set

Edit an existing Data Set to update its name, description, query, and other permitted fields. The editable fields can vary by Data Set category (e.g., Database, API).

Prerequisites:

• Access to Data Center → Data Sets.

• Permission to Edit the target Data Set.

Steps

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Share

• Navigate to the Data Set list.

• Select the target data set, and open the Options context menu for it.

• Click the Edit option.

• The Data Set opens in editable format.

• Edit metadata

  • Data Set name: Update the Service Name.

  • Description: Add or modify the description.

• Modify the query

  • Update the Query directly in the editor or

  • Use Table Information (right panel) and double-click a table/column to auto-insert sample SQL, then refine.

    • Depending on the Data Set category, some fields are read-only. Example (API Data Set): Data Connector Name and Account are not editable.

• Validate

  • Click Validate to execute the updated query.

  • The preview loads under the RESULT tab. The DATA PROTECTION tab is also available for applying/redacting rules.

• Save

  • When validation succeeds, the Save button is enabled. Click Save.

  • A confirmation message appears, and the Data Set is updated.

Notes & Tips:

• Database category: You must validate successfully before you save the edited Data Set.

• Category differences: Steps and editable fields may vary by Data Set category (Database vs API vs others).

• Data Protection: Use the Data Protection window to add redaction, masking, hashing, or date generalization rules before saving.

• Use Ctrl+Space in the Query editor for autocomplete and function hints.

• Use Assist (query helper) to generate/modify SQL quickly, then Validate.

• After significant edits, consider Push to VCS (with a clear commit message) and Publish if downstream consumers rely on this Data Set.

Troubleshooting

• Save disabled: Run Validate first (required for Database Data Sets).

• No preview data: Check filters/parameters or temporarily relax WHERE clauses.

• Read-only fields: Confirm the Data Set category; Data Connector Name (and Account for API) are not editable.

• Validation errors: Verify schema/table names, permissions, and query syntax; use Table Information to insert verified objects.

Deleting a Data Set

Remove a Data Set from the platform when it is no longer needed.

Prerequisites:

• You have permission to Delete Data Sets.

• Confirm the Data Set is not required by active dashboards, APIs, or jobs.

Navigation path: Data Center > Standard Connectors > Data Sets list > Vertical Ellipsis icon next to a Data Set > Options > Delete

Steps to Delete

• Navigate to the Options context menu for the target data set.

• Click the Delete (Remove) icon next to it.

• The Remove Data Set confirmation dialog opens.

• Click Yes to confirm.

• A confirmation message appears, and the selected Data Set is removed from the Data Sets list.

Effects of deletion

• Downstream assets that reference this Data Set (Dashboards/Widgets, Data as API, Data Preparation jobs, etc.) will fail until they are repointed to another Data Set.

• Deletion is typically irreversible from the list. If you need to recover, you must:

  • Pull from VCS (if versions were pushed), or

  • Recreate the Data Set manually.

Best practices

• Publish/Share checks: If the Data Set is published or shared, inform consumers before removal.

• Version safety: Consider Push to VCS with a clear commit message before deleting, so you can restore later.

• Asset audit: Use your team’s catalog/lineage tools to identify dependent dashboards or APIs.

Troubleshooting

• Delete icon disabled: You may lack permission, or the Data Set is locked by a policy; contact an administrator.

• Consumers still see failures after deletion: Update or republish dependent assets to use an alternative Data Set.

• Accidental deletion: Restore via Pull from VCS (if available) or recreate and re-bind consumers.