Data Preview Error in QuickSight During Transformation

While attempting to transform data related to shift timings in Amazon QuickSight, specifically concerning breaks and slot timings, the following error occurred:

No data available for preview.

Details: QuickSight fetches up to 1000 sample rows from each data source table before applying transform operations. However, the transformation process for shift timings resulted in:

There are currently 0 rows of data available for preview as a result of the operations performed on sample rows of data. You may save the dataset and visualize all data from source in Analysis.

Context:

  • Data Source: The dataset contains fields related to shift timings, including breaks and slots.
  • Operations Performed: Transformations involving parsing and manipulating time data from string fields (e.g., Slot, Meal Break, Break-1, Break-2).
  • Problem Encountered: The data preview fails to display any rows after applying the transformations, suggesting that the transformations might be filtering out all sample data or causing errors that prevent data from being processed correctly.

Steps Taken:

  1. Attempted to transform time fields into minutes for comparison.
  2. Applied various functions for parsing and calculating time intervals.
  3. Encountered issues with syntax or logic in transformations, leading to no data being available for preview.

Desired Outcome: Identify the cause of the issue and resolve it to ensure that the dataset preview works correctly, allowing further transformation and analysis of shift timings data.

formulas tried: start_time = substring({Slot}, 0, 5)
end_time = substring({Slot}, 6, 11)
meal_break_start_minutes = parseInt(substring({Meal Break}, 0, 2)) * 60 + parseInt(substring({Meal Break}, 3, 2))

1 Like

Hello @isingla, this is something I have also experienced in QuickSight. In terms of debugging and fixing this, I am unsure of the exact limitation. From my experience, it is due to time constraints and how long it takes for QuickSight to infer the table schema and how long it takes to query the datasource.

Once I have a dataset that has hit this preview limitation, I have been unable to bring it back. You will likely need to save and publish the updates and view a table in an analysis view to see what is being returned from the datasource. I can also tag this topic as a feature request for our support team to see if they can increase these time constraints to improve the preview dataset functionality.

Let me know if you have any further questions. Thank you!

1 Like

Hi @isingla,
It’s been awhile since we last heard from you; did you have any additional questions regarding your initial topic?
If we do not hear back from you within the next 3 business days, I’ll go ahead and close out this topic.

Thank you!