When I try to duplicate a dataset that I have created with “direct query” mode, I get the error:
I am not using SPICE anywhere in this dataset, so I am a bit confused what does SPICE have to do with this issue?!
Has anyone else faced this issue before?! Any ideas on how to resolve this issue?!
Thanks.
Hello @HatAbd9241, is the dataset you are duplicating utilizing a join to another dataset imported in Quick Sight? Click on the edit dataset button when on the original dataset and look at the data preview. If you see a link to a secondary data source, it is possible that the linked dataset is utilizing Spice. Another possibility would be if RLS is applied to the dataset, and RLS is set up with SPICE, and your duplicated dataset is missing a necessary field for viewing permissions.
Let me know if that helps! Those are the main issues I could think of that may be causing this error.
Hello @WLS-DM,
Thank you for your reply.
I figured out what was the issue. The thing is I have migrated this dataset from another environment to a separate environment where I was getting this error. Each environment is individually connected to its backend counterpart. The issue was that when I migrated the dataset from source to target, the definition of the dataset in the target environment was still pointing to the definition of the dataset in the source environment, and in the backend of the source environment I had already added a column which was automatically added to my dataset in the source environment and this column was not available in the target environment. Therefore, duplicating the dataset in the target environment was trying to re-execute the definition of the dataset which included a column that was not present in the backend of the target environment, therefore breaking the schema between the two environments, and finally, the error I was receiving.
As you can see, Quick Sight’s errors are not really informative and this is not the only case where we are either misled by the error messages or we are not getting any useful information out of them. If they want their tool to be widely adopted, they really need to up their game when it comes to such issues.
Thank you.
Hello @HatAbd9241, I am glad you were able to find a solution for this issue. I understand the frustration trying to figure out the error messages, but these things will improve as the functionality and capabilities of Quick Sight continues to grow. For now we will work together on the community to sort through difficult errors and expand the source of information to help future developers and admins avoid dealing with the same issues we have experienced. Good luck building out your dashboards!