Symptom
- Some MDF field it is not appearing in the OData API Data Dictionary of an object that has the API subversion V1.0.
- This is causing errors in the API, such as "[COE0021]Invalid property names"
Exemples:
- createdDate
- mdfsystementityID
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Odata API
Cause
This is an expected behavior if the ''MDF system field in API Mode" as "Removed from all MDF entities" in provisioning, in that case, no matter API subversion is set to v1.0 or v1.1, MDF OData will hide the technical fields in metadata.
Resolution
Also, there was a control in provisioning "MDF system field in API Mode", which has 3 values:
- Removed from all MDF entities regardless of the API Sub Version field setting in the MDF object definition
- Kept for all MDF entities regardless of the API Sub Version field setting in the MDF object definition
- Depends on APISubVersion of MDF object definition: will follow the option on Configure Object Definition
Only when the provisioning set is "Depends on APISubversions of MDF Object Definition", then the object level sub version v1.0 or v1.1 configuration will impact the system property exposed in API.
If your provisioning setting is 'Removed from all MDF entities", this will not respect the v1.0 or v1.1 setting in object definition page and will always remove system property from API metadata.
So to solve this, please set it as "Depends on APISubversions of MDF Object Definition" and keep Position object level API subversion as v1.0, then refresh metadata and mdfSysemEntityID will be exposed.
To change this setting, you can request to your partner or SAP Support.
See Also
You can find more information on the reference guide Implementing the Metadata Framework (MDF)
Keywords
field not visible; OData Dictionary; createdDate; API subversion; technical fields; MDF OData; mdfsystementityID. , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-PRV , Provisioning Changes , Problem
SAP Knowledge Base Article - Public