process-mining
2024.10
true
UiPath logo, featuring letters U and I in white

Process Mining

Automation CloudAutomation Cloud Public SectorAutomation SuiteStandalone
Last updated Dec 18, 2024

Data transformations

Message: [WARNING]: Deprecated functionality The "tests" config has been renamed to "data_tests".

Possible cause

With the introduction of unit tests in dbt version 1.8, the tests: key was renamed to data_tests:. For existing process apps, this results in a deprecation warning that is displayed when running an ingestion or opening Data transformations.
[WARNING]: Deprecated functionality The `tests` config has been renamed to `data_tests`. Please see https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax for more information.

Solution

For default process apps, you can rename the occurrences of the tests: config to data_tests: in the dbt_project.yml and the sources.yml files to fix this. For customized process apps, this can be present in other .yml files as well.

Check out the official dbt documentation on the New data_tests: syntax for more information.

Preview does not change after changing the query

It can occur that the Preview does not change after you changed the query and run the file.

Possible cause

The sql file is identical to the one in dbt, as it has not been updated since the last run. If you run the file again, no changes will be detected and therefore the Preview table won't be updated. For example, if you add a WHERE condition and run the file, the Preview will only show the filtered records. However, if you remove this WHERE condition and run the file again, the Preview will still only display the previously filtered records, when it should actually show all records.

Solution

Add, or change, a comment in the SQL file. This will force a dbt run and the Preview will be updated.

Message: The selection criterion does not match any nodes. Nothing to do.

The following warning messages are displayed in the ingestion log.
docs image
When you get the two warning messages The selection criterion "+<file>.state:modified+" does not match any nodes and Nothing to do. Try checking your model configs and model specifications args, it means that no changes were detected compared to the last time the queries were run. The Preview panels are showing the most up-to-date version of the data.

To force a complete re-run of your queries, select Apply to dashboards.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.