- Newest
- Most votes
- Most comments
The issue you're experiencing with the new data preparation experience in Amazon Quick Sight (part of Amazon Quick Suite) appears to be related to the recently released visual data preparation feature.
Amazon Quick Sight recently launched a new data preparation experience that allows business users to perform advanced data transformations without writing complex code. This includes operations like cleaning, transforming, and combining data in multi-step workflows. While this new feature is designed to make data preparation more accessible, it seems you're encountering an INTERNAL_SERVICE_ERROR when trying to use it with S3 data sources.
Your workaround of switching back to the legacy experience is a good temporary solution. Since the legacy experience is working correctly for your decimal conversions, you might want to continue using it until this issue is resolved.
For this specific error, you might want to try the following:
- Verify that your S3 data source permissions are correctly configured
- Check if the data format is compatible with the new experience
- Try simplifying your transformation workflow initially, then gradually add complexity
- If you're using boolean fields in your dataset, ensure they're properly formatted as the new experience might handle them differently
If the problem persists, you might need to contact AWS Support as this could be related to the recent rollout of the new data preparation experience. The INTERNAL_SERVICE_ERROR suggests there might be an issue on the service side rather than with your specific configuration.
Sources
Amazon Quick Sight announces the general availability of a new data preparation experience - AWS
Quicksight Boolean issue | AWS re:Post
Transform and visualize your data preparation flow in Amazon Quick Sight without SQL | AWS Business Intelligence Blog
Reimagine business intelligence: Amazon QuickSight evolves to Amazon Quick Suite | AWS Business Intelligence Blog
answered a year ago
We will look into this issue and give you a response by Nov 7th.
answered a year ago
@SGuzman We would like to investigate further. Can you create an AWS support ticket and share your S3 manifest file used for this connection?
answered a year ago
Relevant content
- AWS OFFICIALUpdated 10 months ago
