Navigating Date Filtering Challenges in ESHOPMAN Admin: A Deep Dive into `view_configurations`

As experts at Move My Store, we constantly monitor and share insights from the ESHOPMAN community to help merchants and developers optimize their headless commerce operations. A recent discussion highlighted a significant challenge concerning date filtering within the ESHOPMAN Admin Dashboard, particularly when the view_configurations feature flag is enabled. This issue, while actively being addressed by the ESHOPMAN team, is crucial for anyone managing storefront data, especially orders, through the HubSpot-integrated platform.

Understanding the ESHOPMAN Admin Date Filter Bug

The ESHOPMAN Admin Dashboard, powered by Node.js/TypeScript and designed for seamless storefront management within HubSpot, offers robust data table functionalities. However, a specific bug has been identified that impacts the custom date filtering mechanism in configurable DataTables, such as the Orders list. This bug manifests in three distinct ways, significantly affecting data retrieval and user experience.

1. Dropped Date Picker Input

When attempting to apply a custom "Starting" date filter in a DataTable (e.g., for 'Created at' on the Orders list), users might experience the selected date input being dropped. The filter editor closes prematurely, and the URL parameter for the date filter becomes empty (o_created_at={}). This prevents the filter from being applied correctly and makes the filter chip unusable.

// Observed URL behavior after picking a start date
o_created_at={}

Initially, the URL might briefly show the selected date with a $gte (greater than or equal) parameter, but it quickly reverts, indicating an issue with how the Admin UI processes and persists the date selection.

2. Incorrect End Date Calculation (Midnight Issue)

Another critical aspect of this bug involves how the "Ending" date in a custom range is interpreted. When a user selects the same day for both "Starting" and "Ending" dates, or even a wider range, the $lte (less than or equal) parameter sent to the ESHOPMAN Admin API is incorrectly set to the local midnight of the start day. For example, if October 2nd is selected as both the start and end date (in a UTC+7 timezone), the API request might incorrectly send:

created_at[$gte]=2026-10-01T17:00:00.000Z
created_at[$lte]=2026-10-01T17:00:00.000Z

This effectively sets the end date to the beginning of the selected period, resulting in zero matching orders for what should be a full day's range. The expected behavior is for the filter to cover the entire day, from 00:00:00.000 of the start day through 23:59:59.999 of the end day (local time). The ESHOPMAN Admin API itself handles the correct date ranges, implying the issue lies within the UI's date range construction.

3. URL Table State Wiped on Load

Perhaps one of the most frustrating aspects for users is the inability to maintain table state across navigation or reloads. If a user accesses the Orders list with pre-configured filters in the URL (e.g., from a shared link, a browser reload, or using the 'Back' button), the ESHOPMAN Admin Dashboard will wipe these parameters upon loading. For instance, a URL like /app/orders?o_order=-id&o_created_at={">"}:"...","$lte":"..."} will be rewritten to /app/orders?o_order=-id, effectively clearing all date filters and displaying every order. This significantly hinders shareability, bookmarking, and efficient workflow for merchants managing their HubSpot-deployed storefronts.

Impact and What This Means for ESHOPMAN Users

This bug primarily affects users who rely on precise date filtering for order management, reporting, and data analysis within the ESHOPMAN Admin Dashboard, especially when leveraging the view_configurations feature. It can lead to incorrect data visibility, wasted time re-applying filters, and a less fluid user experience. While the ESHOPMAN team is actively triaging and working on a resolution for this issue in version 2.0 and beyond, understanding these behaviors is crucial for developers and merchants to anticipate and navigate these limitations in the interim.

At Move My Store, we recommend staying updated with ESHOPMAN's official releases and community channels for the latest fixes and workarounds. This insight serves as a heads-up to the community, ensuring transparency and aiding in the effective management of your ESHOPMAN-powered headless commerce platform.