When the expiration Time for a given table is reached, that table will be deleted automatically.
This is a very tedious and time consuming process that is really quite painful.
This also, doesn't work well with deploying Azure Data Factories from Visual Studio using a config file.
I recommend to add public method to call a complete refresh or better yet, adapt the ng On Changes() routine to look for new changes to other chart settings and if outside of data/dataset changes call refresh() instead of just an update().
@Shadowlauch - The above causes a null data error: Model Sublabel Component.html:59 ERROR Type Error: Cannot read property 'data' of undefined at charts.js:90 at Each () at Base Chart Directive.webpack Jsonp.../../../../ng2-charts/charts/
Idea from @Jeff_J_Jordan via Twitter: Currently in Azure Data Factory once a dataset is deployed, you cannot change the availability for the dataset.
If you attempt to change the availability you get the following error message: “Updating the availability section of a Dataset is not supported.
The role field is not required when this field is set.
If that view is updated by any user, access to the view needs to be granted again via an update operation.[Optional] The default lifetime of all tables in the dataset, in milliseconds.
The minimum value is 3600000 milliseconds (one hour).
Once this property is set, all newly-created tables in the dataset will have an expiration Time property set to the creation time plus the value in this property, and changing the value will only affect new tables, not existing ones.
Existing availability configuration: Frequency=Day, Interval=1, Anchor Date Time=01/01/0001 , Offset=, Style=Start Of Interval, new availability configuration: Frequency=Day, Interval=1, Anchor Date Time=01/01/0001 , Offset=, Style=Start Of Interval.” Take Daylight Savings Time for example, you want to run your datasets at midnight CST (UTC -) but during DST it becomes am CST.