When you create or edit a dataset, you can choose which fields are available to your workflows. If a selected field, entity, or relationship later changes at the source, Streamline identifies the issue and helps you reconnect the dataset without rebuilding it.
This feature is available to all Streamline customers.
Who Has Access?
| Role or access level | What you can do |
|---|---|
| Admin or Manager | Create and edit datasets, choose fields, and reconnect affected items. |
| Builder | View issues on the dataset's Status tab. |
Builders can review what changed and see the affected project and session counts. They cannot repair the dataset, and the Reconnect action is not shown.
Key Capabilities
-
Choose the fields workflows can use. Include only the fields needed in Search Data and Deliver Data steps.
-
See what changed. The Status tab identifies deleted entities, fields, or relationships, as well as changes to field type, required status, or write access.
-
Review the impact. Each issue shows the number of affected projects and sessions.
-
Reconnect changed data. Map an affected entity, field, or relationship to its replacement without recreating the dataset.
Update Dataset Fields
You can update the field selection on an existing dataset.
- Go to Data > Datasets.
- Open the dataset you want to edit.
- Select Actions > Edit.
- Edit the dataset options, such as its name or entities, as needed. Then select Next.
- Select the fields that should be available to workflows.
- Select Update.
Note: Required fields and primary key fields cannot be excluded.
Fields you exclude do not appear in Search Data or Deliver Data field selectors. Changes to an excluded field do not create an issue for that dataset.
Find Dataset Issues
Dataset issues are detected after an automatic or manual rescan of the data source connection.
- Go to Integrations and open the connection used by the dataset.
- Select Rescan.
- Go to Data > Datasets.
- Open a dataset with an issue indicator.
- Select the Status tab to review what changed and the number of affected projects and sessions.
Note: Rescans start from Integrations, not from the dataset's Status tab. It may take a few seconds for a new issue to appear after a rescan.
What Happens When an Affected Field Is Used
If a field issue remains unresolved and a session reaches a Search Data or Deliver Data step that uses that field, the step fails. The participant sees a Workflow failed message and is directed to contact the workflow administrator.
Repair the dataset before running the session again.
Repair a Dataset
Use Reconnect to map changed source items to their replacements.
- Open the affected dataset and select Status.
- Review the open issue and select Reconnect.
- In Reconnect entity, select Suggest mapping or choose a replacement entity manually.
- In Reconnect fields, select Suggest mapping or map affected fields manually. Review each suggested mapping before continuing.
- If shown, map affected relationships to their replacements.
- In Confirm and save, review the mappings, then select Confirm and save.
You can save a partial repair when at least one item is mapped. Any item you do not map remains open on the Status tab.
Important: A saved reconnect cannot be rolled back in Streamline. Review each mapping before you select Confirm and save.
Clear an Issue by Restoring a Field
If a field was deleted by mistake, you may be able to clear the issue without reconnecting it.
- Restore the field in the source system.
- Go to Integrations and rescan the connection.
- Return to the dataset's Status tab and confirm the field issue has cleared.
Restoring a deleted relationship may not clear the issue automatically. If it remains open, use Reconnect.
Feature Considerations
-
Existing datasets that have not been updated to use field selection continue to include all source fields.
-
File entities do not appear in Customize fields.
-
Drift detection and dataset repair are not supported for Redox or Power BI data sources.
-
Impact is shown as project and session counts. The Status tab does not list or link to individual projects.
-
Dataset issues cannot be dismissed or ignored.
-
Issue indicators do not appear in the Search Data or Deliver Data setup screens. Review the dataset's Status tab.
-
Changes may take up to 60 seconds to appear in the workflow builder after a repair.
Compliance
Dataset issue details can include source entity and field names. They do not include record values or other row data.
Troubleshooting
| Issue | Resolution |
|---|---|
| A source change does not appear on Status | Confirm the connection rescan finished, then wait a few seconds and check again. |
| Impact shows no affected projects or sessions | Wait 10 to 30 seconds and reopen the dataset. |
| Reconnect is not available | Builders can view dataset issues but cannot repair them. An Admin or Manager must reconnect the affected items. |
| The repair does not save | Confirm at least one item is mapped and that every mapping you entered is valid. One invalid mapping prevents the full set from being saved. |
| Multiple fields are mapped to the same replacement | Each replacement field can stand in for only one original field. Choose a different replacement field or leave the original field unmapped. |
| The workflow builder still shows old field information | Wait up to 60 seconds, then reopen the builder. |
| A restored relationship still shows as deleted | Use Reconnect to map the relationship. Restoring a relationship may not clear the issue automatically. |
Summary
Use Customize fields to limit a dataset to the fields your workflows need. When a selected source item changes, review the dataset's Status tab and use Reconnect to repair it.
Comments
0 comments
Please sign in to leave a comment.