Autosave error with Calculated field

We keep getting this error and the analysis isn’t being saved:

“Autosave appears to be having some trouble right now. Do you want to continue without saving or try to refresh this analysis to go to the stored version.”

We aren’t able to manually save it either.

This happens when we create a calculated field like this:

> ifelse(
> ${PlotMetric} = 'rev', SUM(rev),
> ${PlotMetric} = 'purchasers', distinct_count(uidn),
> )

The issue is not because of anyone else using it or slow network issue.

I would suggest logging out. Logging back it. Making sure auto save it on. Making sure no one else is editing it. And then trying.

1 Like

We tried that and even tried recreating a new analysis with a new dataset and that issue persisted. It only happens with that sort of calculated field. For example a normal sum calculated field works and saves fine but, when we use something like the above ifelse statement, we get the autosave issue.

We made sure there are no network issues, no additional or shared users and restarted and recreated it but we haven’t had any luck.

Something like this works for me.

${CustomParam} = 'rev', sum({arrival_timestamp_int}),
${CustomParam} = 'purchasers', distinct_count({client_id}),

Can you please make sure the sum is lowercase.

1 Like

@Max I am having the same problem. I can confirm that the sum() function is lowercase and all my functions get highlighted in the blue colour which signifies that Quicksight recognizes it. I have also tried to make a ‘Breakdown’ option for my plots where the user can select different breakdown options and the plot colours will change based on the selection.

To do this, I created a dataset parameter named ‘Breakdown’ and linked this to an Analysis parameter which I also called ‘Breakdown’ and I created a Control so that the user can choose the Breakdown option. Now, the last step would be to create the custom field that will identify which field in the dataset to choose as the Colour in the plot, based on the input in the control but I keep getting this Autosave Failure error. My Calculated field looks like this:

${Breakdown} = 'game', {game},
${Breakdown} = 'network', {network},
${Breakdown} = 'platform', {platform},

As soon as I try so save it, I get Autosave Failure and it prompts me to refresh to report. When I refresh it, my calculated field is gone. I have also tried working with Autosave turned off and this allows me to make changes, but as soon as I go to manually save the report it saves the old version, so my changes are once again lost. I am able to make a simpler calculated field, for example something like sum(revenue), and this gives me no problems. But for some reason as soon as I try using the ifelse() with the Breakdown parameter I run into this problem.

1 Like

Hi @jovanaV - If you still see this issue, I would recommend filing a case with AWS Support where we can dive into the details to help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!