Hello @Ali_B, these are all great feature suggestions that would improve the management of date fields in Quick Sight. While we are unable to provide implementation timelines for feature requests, I can at least suggest some alternative options that could allow you to handle these expectations for now.
- Manage this in SQL for the time being. I understand the limitations here will be that the value is going to be converted to a string rather than a datetime datatype, but it would at least allow for more customization on your visuals. Depending on the datasource you utilize, the calculation may differ slightly, but the monthname calculation is going to be the best bet. If you are unable to utilize custom SQL, you can always utilize an ifelse statement in a calculated field to return a string month name or weekday name depending on the returned value of the extract function.
- Currently, date formats vary depending on the datasource you are utilizing. The parseDate function docs have a great list of date formats depending on the database you are connecting to. There is also helpful information in the Support Date Formats documentation. There is also some great information about formatting dates in this blog post.
- Some options currently exist for formatting parameter dates. There are some granularity options in the edit parameter section:
You can also customize the date format within the control you are linking the parameter to:
Last option would be to pull the parameter into a calculated field or insight and use a function like formatDate to change the output.
These are some alternative options to handle the recommended functionality for the time being. I would recommend utilizing these suggestions for any time sensitive requirements. You can also keep an eye on the What’s New tab to stay up-to-date with new feature rollouts for Quick Sight.
I will archive this feature-request topic for our support team. Thank you for your feedback!