Frequently asked questions
1. Why is Quick Sight launching the new data preparation experience before achieving full feature parity with the legacy experience?
The new data preparation experience was developed through extensive customer collaboration to address real-world analytics challenges. The initial launch prioritizes:
Enhanced capabilities
-
Visual transformation workflows
-
Improved process transparency
-
Advanced preparation techniques through Divergence
-
Powerful new features like Append, Aggregate, and Pivot
Flexible adoption
Users can choose between experiences before publishing datasets, ensuring uninterrupted workflows while teams transition at their own pace. This approach allows immediate access to new capabilities while maintaining support for specialized requirements through the legacy experience.
2. Will features currently available only in the legacy experience be added to the new experience?
Yes. Quick Sight is actively working to incorporate legacy features into the new experience.
3. How do API changes affect existing dataset creation scripts?
Quick Sight maintains backwards compatibility while introducing new capabilities:
-
Existing Scripts: Legacy API scripts will continue to function, creating datasets in the legacy experience
-
API Naming: Current API names remain unchanged
-
New Functionality: Additional API formats support the new experience's enhanced capabilities
-
Documentation: Complete API specifications for the new experience are available in our API reference
4. Can datasets be converted between experiences after publication?
-
Future Migration Path: Quick Sight will add a feature in the future to easily migrate legacy datasets to the new experience.
-
One-Way Process: Converting datasets from the new experience to legacy format isn't supported due to advanced feature dependencies
