When consuming an ORDS-generated OpenAPI 3 specification in VBCS from a HTTP hosted specification, OperationId is required for the Endpoints to be useful within Visual Builder. When using the Static Option - copying the full OpenAPI specification - VBCS offers to auto-generate OperationIds, such as postEmployees or getDepartments, as a workaround. This is not an option when using dynamic metadata, where it reports those OperationIds as missing.
Per https://swagger.io/docs/specification/paths-and-operations/, OperationId is “an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.”
It would be very useful to be able to set the OperationIds from within ORDS - to allow for the dynamic option and have control over the naming. Is this possible?