Best Of

Hi Charles

This is not possible 'out of the box' in Data Studio, but it would be possible to write a custom step to generate an XML file or call an API directly:

https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/extend-data-studio-functionality/use-the-sdk/

Coming soon it will be possible to write a Custom exporter for the Export step

I wish the cell style would persist when exporting to Excel - would be nice to keep the colours.

Hi James

You are correct, a Group then Union is how I would achieve this:

1. Group
2. Delete default 'Count' aggregate and add a new aggregate
3. Select 'Multiple' and set Name to blank
4. Select all (numeric) columns
5. set Aggregate to Sum and apply

—> Then Union this with the existing data

Optional, but depending on what you are doing with these totals, you could format / style the totals rows using a Transform before the Union. Example comma separating these likely large numbers and coloring the totals row to make it stand out:

SetCellStyle(

_RegexReplace(value, '(?:^|\G)(\d{1,3})(?=(\d{3})+(?:.\d+)?$)', '$1,', false),

'Success'

)

https://docs.experianaperture.io/data-quality/aperture-data-studio-v2/get-started/create-functions/#function-script-editor

@Mahulima Thanks for confirming. Yes I think that it is this behaviour that is causing it to become very slow.

I've raised this and will get it resolved as soon as possible.

Regards,

Ian

@Ian Hayden Hi Ian I have access to 30+ spaces and by default are are selected . May be because of default settings of selecting all spaces making it slower.

Thanks Mahulima we will look into it.

Thank you so much Ian, that has worked! Thanks for raising this as a bug too.

Hi Sarah,

Josh forwarded me your workflow and I've taken a look at it.

The problem is that the StudentInitiative_1 source was changed and one of it's fields was renamed (by the looks of it INITIATIVEID changed to STUINITID). This field is used in its downstream transform step and the "Filter For Coverage" step which invalidates these steps and the workflow. This check is happening at publish/run time, but not when you open the workflow. When you open the workflow or change a source Data Studio should detect that the source has changed and prompt you to remap the columns. I will raise a bug to look into why this has not happened in this case.

The easiest workaround is to switch the source to StudentInitiative (which shares the same schema), which will detect the change and prompt to remap the columns, then change it back to StudentInitiative_1 (which does not need remapping again). The workflow should become valid again.

Best Regards,

Ian

To solve this you should be able to use the Stop execution when refresh failed option on the Source steps in your workflow (available from Aperture 2.8.4 onwards). This has the effect of causing the workflow to fail if auto-refresh on the source from the External System fails for any reason.

With the setting enabled, my job execution will fail when the External System cannot be reached:

Without the setting enabled (the default), the job will complete with a warning in the execution details:

You can also add an Automation to notify / alert (or carry out some other action) when any of these failures or warnings occur, for example:

Which will give the send the following notification:

Note that the "Send notification" action and notifications inbox in my screenshot above is new in version 2.12, but in prior versions you can still send emails or trigger workflows / schedules