Azure / Azure/data-api-builder

[Bug]: OpenAPI and $filter for dates

Ouverte
#2,783 5 commentaires 6 réactions 3 personnes assignées Voir sur GitHub

@JerryNixon y travaille déjà.

Depuis le 7/7/2026.

  • #3706 par @copilot-swe-agent — ouverte
2.2 bug cri open-api triage
Langage dominant
C#
Étoiles
1.5k
Forks
372
Merge moyen
3 j 22 h
PR mergées (30 j)
9

Description

What happened?

Hi Team,

We've developed a custom frontend and backend solution to manage API creation on our API Management platform, utilizing Data API Builder (DAB) to select fields and apply dynamic and fixed filters to APIs.

The issue arises with certain MSSQL tables using the datetime(2) data type. In the OpenAPI specification generated by DAB, these columns are represented as string types without a specified format.

OpenAPI exposed by DAB
Image

For exposure through REST we don't have issues, but there's now a requirement to add filters based on those dates.
The data within the database looks like a normal date (not ISO8601 compliant) and is exposed through DAB rest endpoint as follows:

Image

According to the documentation, date values should not be enclosed in quotes. However, when dynamically constructing the $filter parameter for DAB, we currently lack a method to distinguish whether a field is a true string or a date field.

Image

One proposed solution was to omit quotes for non-eq comparisons, but this approach fails when an exact date match is required.

Any insights or suggestions to address this issue would be appreciated.

Best Regards,
Siebe

Version

1.3.19

What database are you using?

Azure SQL

What hosting model are you using?

Container Apps

Which API approach are you accessing DAB through?

REST

Relevant log output

Code of Conduct
  • I agree to follow this project's Code of Conduct

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.