Deprecated. Returns the xml representation of an entry depending on the operation and the HTTP method that must be used when the xml is sent to the SAP server in an HTTP request Sample usage: Creating an xml from an entry that can be sent to the server to create or update the data in the backend defined by the key values. The collection must have the sap:creatable or sap:updatable attribute set to true to succeed (depending on the operation). SDMODataEntryXML* entryAsXmlAndHttpMethod = sdmBuildODataEntryXML(entry, ENTRY_OPERATION_UPDATE_FULL, serviceDocument, NO);
The entry from which the function creates its xml representation (
The operation that should be executed on the server side. Possible values are: ENTRY_OPERATION_CREATE: the xml contains the data of a new entry that should be created in the backend ENTRY_OPERATION_UPDATE_FULL: the xml contains the data of an existing entry in the backend. All the updatable fields will be updated in the backend. If an updatable field does not appear in the xml, the value in the backend that is assigned to the missing field will be overwritten with its default value. The entry to be updated is identified by the key fields of the xml. ENTRY_OPERATION_UPDATE_INCREMENTAL: the xml contains the data of an existing entry in the backend. Only those properties are updated in the backend that are indicated in the xml and leaves anything untouched in the backend. ENTRY_OPERATION_ARCHIVE: Used when an entry should be saved as an xml file and is not sent to the server. This causes the builder to add the links and icon url (if present) too to the xml.
The service document instance. See
If the parameter value is YES, all inline entries and/or feeds will be serialized that belong to the entry being serialized.
Returns the xml representation of an entry for the given operation and the HTTP method that must be used when sending the entry to a SAP server in an HTTP request.