create-odata-query

To build safe OData queries for Directum RX, you derive the correct entity set names and property schema from metadata, then apply safe construction rules to prevent injection. This ensures $filter, $select, and $expand parameters match service expectations.

Predicting the correct OData entity set name relies on the entity schema and IntegrationServiceName mapping, typically following the pattern I{IntegrationServiceName}s. This ensures your OData requests target the correct Directum RX data structure.

Yes, you can use $expand and $select together. The process extracts the entity property schema, including field names and navigation properties, ensuring your expanded and selected fields correctly align with what the Integration Service expects.

The best way to filter safely is by enforcing safe query construction rules that validate metadata and ensure proper quoting and null checks. This prevents malformed $filter clauses and OData injection vulnerabilities.

OData queries fail to return navigation properties when the entity property schema is not properly extracted or validated. You must locate the IntegrationServiceName in the .mtd metadata and run consistency checks to align $expand parameters.

Yes, you need .mtd metadata files. They are required for locating the IntegrationServiceName, extracting the entity property schema, and running post-change consistency checks to validate your OData query structure.