Experian Data Quality Community
-
Customizing your Dashboard with the Custom content widget
Data Studio Dashboards can be configured by adding, ordering and resizing different widgets including Views and Charts. One of these widgets is the Custom content widget: https://docs.experianaperture.io/data-quality/hosted-aperture-data-studio/data-studio-objects/dashboards/#custom-content~customizing-dashboards Firstly…
-
Add a delay in automation between when a trigger is triggered and when the action is carried out.
Hi, I currently have a number of schedules and automations running in order to run some sequential steps in a find duplicate process. I have an initial schedule that refreshes data and then an automation that detects the datasets are refreshed and kicks off a workflow that validates that the date stamp on the data is…
-
Suggestion: Auto-Save rules in a validation step
Hi, I have come across something rather infuriating this afternoon whilst creating a number of validation rules within the same rule group. Having spent the best part of 2 hours creating around 20 rules I briefly lost connection, after reconnecting I had to navigate back to the validate step. … all my rules were gone…. Can…
-
Custom email notifications to include failing validation rules
Hi, I am wanting to set up email notification that fire when a data quality workflow validation step returns failures. I have been able to set up the email notification itself but i want to include the actual rule and number of fails in the body of the email so it gives some context as to where to investigate. a simple…
-
Sticky Notes attached to Workflow step
Just a thought… but it would be really nice if Sticky notes could be pinned to workflow steps (I always provide decisions or descriptions of steps as part of knowledge transfer). That way if I move my workflow step the Sticky note comment moves with it (or worse, someone hits the auto-arrange button and now my Sticky notes…
-
Pushdown Processing on a pivot
Hi, In testing Pushdown Processing today, I hit a couple of errors. The first is simple to workaround by removing it (but would be awesome if the generation understood to omit) - the dataset query had a semi-colon at the end, which pushdown processing then put it's "as R0" after: The second I'm still at a bit of a loss. I…
