Decrease the time granularity on datetime picker

Hi,

I’ve identified a workaround to address the issue described. Please follow these steps:

  1. Connect to your database.
  2. Navigate to the strapi_core_store_settings table.
  3. Find the row corresponding to the API of the collection you’re attempting to modify. It will resemble something like: plugin_content_manager_configuration_content_types::api::post.post.
  4. Modify the content of the value column by removing the step field for the field that triggers the error, for example plannedAt.

Once done, you should be able to configure the view without encountering errors.