Refreshes for Datasets containing Calculated Tables over Direct Query to AS started failing Mar 30th

PunChili Thanks for the clear instructions.

This feature is working for me as well.  The step related to creating a new connection supporting SSO is a bit odd.  This shoudln't be necessary, considering that the scheduled refresh is the point when the calculation happens and, at that moment in time, the *only* applicable user credentials are the ones that are well known (I have "import" queries where we've already specified via OAUTH for the refreshing of the final model).

In any case, I'm glad we can get this working.

I was a bit disappointed to find that there is a 1 MM limit on the number of rows that can be pulled into a calculated table.  It seems like this should be a lot higher, in cases where we are just moving data from one dataset to another, over direct query.  I think there is a place in the service to override the 1 MM default.  We may try increasing to 50 MM.