data-api-builder-relations

To define reciprocal relationships in Data API Builder, you create inverse relationship pairs for entities within your dab-config.json file. This ensures explicit source and target fields are mapped to support bidirectional navigation in both REST and GraphQL endpoints.

Configuring many-to-many linking objects for DAB endpoints requires defining the joining table within your dab-config.json. You must ensure consistent reciprocal pairs and explicit field mappings to properly support navigation across both REST and GraphQL APIs.

Explicit source and target fields are required for Data API Builder relationships to guarantee clarity and reliability. Defining source.fields and target.fields ensures that reciprocal pairs remain synchronized for accurate bidirectional navigation in REST and GraphQL.

You should enforce bidirectional navigation in dab-config.json whenever you connect tables or define navigation properties. Applying reciprocal relationships ensures consistent API behavior and allows clients to traverse data seamlessly across REST and GraphQL endpoints.

Data API Builder supports reciprocal pairs for GraphQL APIs by enforcing them within your dab-config.json configuration. Applying this pattern ensures that both sides of a relationship remain in sync for consistent bidirectional data navigation.