| D toc |
|---|
| Excerpt |
|---|
This section describes how to identify dependency issues between your current recipe and other recipes or datasets and includes general steps for fixing them. |
Where possible, changes made in one dataset or recipe propagate to the datasets that consume it.Datasets Datasets that join, union, or lookup against your dataset are likely to be impacted if you delete columns or rows or otherwise change the data. In some cases, the recipes of these dependent datasets can break.
This section describes how to identify these dependency issues and includes general steps for fixing them.
How to Identify
Dependent datasets
When making edits to a recipe, you can verify if your changes potentially impact other recipes or reference datasets that rely on it. In the Transformer page, click the drop-down next to the current dataset's name to open the Recipe Navigator. Select the Flow View tab.
| Tip |
|---|
Tip: If your current dataset is connected to datasets to the right of it, those datasets are dependent on the current one. After you make changes to the current one, you should use the Recipe Navigator to open recipes and datasets that are connected to it and to the right of it in flow view. |
See Recipe Navigator.
Broken data integrations
When you make some changes in an upstream recipe or dataset, the recipes for any downstream datasets can break, such that you cannot generate satisfactory results. In the downstream recipe, you may see errors in the Recipe panel, such as the following:
...
- Open the object where the column was dropped:
- If the recipe or dataset is from the same flow, you can use the Recipe Navigator in the Transformer Page. See Recipe Navigator.
- If the recipe or dataset is in a different flow, use the Flows page to locate it (
REF_CAL.txtin the above). See Flows Page.
- In the Flow View tab, open the dataset referenced in the error message.
In the Recipe panel, locate the step where the column was removed.
Fix the issue. Details are below.
...
Fix the issue in the source dataset. Verify that the change does not impact other datasets.
Info NOTE: If you fix the issue in the source dataset, you should verify if any other downstream datasets are impacted by this change.
Change the input dataset to use a dataset that is not broken.
Tip Tip: If you must freeze the data in the dataset that you are using as an input, you can create a copy of the dataset as a snapshot . See from the Dataset Details Pagepage.
To use the copy, repair or rebuild the integration using the copied version.
- Fix the issue in the dataset that depends on it. In this case, you must redefine the transformation that brings in the data.
| D s also | ||||
|---|---|---|---|---|
|
