Symptom
- Data Flow execution fails with the error message: "The property 'column', used in a query expression, is not defined in type 'object'."
- The error message is accompanied by a HTTP/1.1 400 Bad Request response.
Environment
SAP Datasphere
Reproducing the Issue
Executing a Data Flow where source object is from a Generic OData connection type.
Cause
The issue arises from a metadata unsync problem in the Data Flow.
The source object was changed, and Data Flow now expects an inexistent column from object.
Resolution
- Verify if there is a metadata mismatch between current Source Object and a new one being loaded from same Connection/Object.
- Confirm that the source object loads same amount of fields.
- If yes, make sure column from error is present in Source's metadata.
- In case missing, verify if the OData service could re-include the missing column again, or re-design the Data Flow to remove the non-existing columns.
See Also
Keywords
Data Flow, Execution Error, Undefined Property, CompanyCode, JournalEntryEmissions, Metadata Issue, OData Connection, Column Missing, Error 400, Bad Request. , KBA , DS-DI-DF , Data Flows , Known Error
Product
SAP Datasphere all versions