added xlsx js for excel

utils/buildQuery.util.js

@@ -24,9 +24,11 @@ const AUDIT_ID_FIELDS = new Set(["createdBy", "updatedBy", "deletedBy"]);
  *   "column reference is ambiguous" as soon as a query joins another table
  *   that happens to share a column name (e.g. Users + UserGroups both have
  *   is_active/createdAt/updatedAt/deletedAt).
+ * @param {Set<string>} [dateFields] - fields whose picklist values are
+ *   calendar days (see below) — matched by range, not substring.
  * @returns {Object} Sequelize where clause
  */
-function buildWhere(filters = [], allowedFields = new Set(), parentAlias = null) {
+function buildWhere(filters = [], allowedFields = new Set(), parentAlias = null, dateFields = new Set()) {
   const where = [];
 
   for (const { id, value } of filters) {
@@ -42,6 +44,31 @@ function buildWhere(filters = [], allowedFields = new Set(), parentAlias = null)
 
     const qualifiedCol = parentAlias ? `${parentAlias}.${id}` : id;
 
+    // Date/timestamp columns (createdAt, updatedAt, ...) — the filter sheet's
+    // picklist values are whole calendar days (e.g. "2026-07-16"), but the
+    // column itself is a full timestamp. Casting the timestamp to TEXT and
+    // doing a substring iLike match against just the date portion is a loose
+    // match: it also picks up every OTHER row whose time-of-day component
+    // happens to render into digits that appear elsewhere in the cast string,
+    // so a single selected day can silently pull in unrelated rows. Match by
+    // an explicit [dayStart, nextDayStart) range on the real column instead —
+    // exact, and immune to how the DB happens to stringify the timestamp.
+    if (dateFields.has(id) && !id.startsWith("personal_info.")) {
+      const conditions = values.map((v) => {
+        const datePart = String(v).slice(0, 10);
+        const dayStart = new Date(`${datePart}T00:00:00.000Z`);
+        const dayEnd = new Date(dayStart.getTime() + 24 * 60 * 60 * 1000);
+
+        return Sequelize.where(Sequelize.col(qualifiedCol), {
+          [Op.gte]: dayStart,
+          [Op.lt]: dayEnd,
+        });
+      });
+
+      where.push({ [Op.or]: conditions });
+      continue;
+    }
+
     const conditions = values.map((v) =>
       id.startsWith("personal_info.")
         ? Sequelize.where(
@@ -114,17 +141,19 @@ function buildOrder(sort = [], allowedFields = new Set(), computedFields = new S
  *
  * @param {Array} filters
  * @param {Array} sort
+ * @param {Array} [dateFields] - fields to match by day-range instead of substring
  * @returns {{ where: Object, order: Array }}
  */
-function buildQuery(filters = [], sort = [], allowedFields = [], computedFields = [], parentAlias = null) {
+function buildQuery(filters = [], sort = [], allowedFields = [], computedFields = [], parentAlias = null, dateFields = []) {
   const fieldSet = new Set(allowedFields);
   const computedSet = new Set(computedFields);
   const orderFieldSet = new Set([...allowedFields, ...computedFields]);
+  const dateFieldSet = new Set(dateFields);
 
   return {
     // Computed (subquery/literal) columns aren't real table columns — filtering
     // via Sequelize.col() would error, so only allow them in ORDER BY, not WHERE.
-    where: buildWhere(filters, fieldSet, parentAlias),
+    where: buildWhere(filters, fieldSet, parentAlias, dateFieldSet),
     order: buildOrder(sort, orderFieldSet, computedSet, parentAlias),
   };
 }