on 06-15-2017 9:48 AM
Hi ,
I am facing same issue did u got the solution.
Thanks,
Jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why exactly do you need it to explicitly state nullable=true? From the Oasis OData specification:
The edm:Property element MAY contain the Nullable attribute whose Boolean value specifies whether a value is required for the property.
If no value is specified for a property whose Type attribute does not specify a collection, the Nullable attribute defaults to true. If no value is specified for a property whose Type attribute specifies a collection, the client cannot assume any default value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas Jung
Thank you for the reply.
We are using this service in SAP GATEWAY, Gateway is setting Nullable false for all values this is causing an issue with date field in Gateway, since gateway cannot accept null as a valid date.
Our landscape is HANA table that is exposed as xsOdata service that in turn is consumed by gateway and exposed to the outside world. HANA table has NULL values for a few Dates. We are generating these services using the OSCI (/IWBEP/OCI_SRV_GEN).
By setting nullable as true we can tell gateway that this variables accepts null values.Thus is in turn solving our issue with date field.
If any other alternatives solutions please do let me know.
User | Count |
---|---|
81 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.