Action Invocation Action parameter values are encoded in a single JSON object in the request body. Each non-binding parameter value is encoded as a separate name/value pair in this JSON object. The name is the name of the parameter. The value is the parameter value in the JSON representation appropriate for its type. Entity typed parameter values MAY include a subset of the properties, or just the , as appropriate to the action. Any parameter values not specified in the JSON object are assumed to have the null value. Example 44: { "param1": 42, "param2": { "Street": "One Microsoft Way", "Zip": }, "param3": [ 1, 42, 99 ], "param4": null } In order to invoke an action with no non-binding parameters, the client passes an empty JSON object in the body of the request. 4.01 Services MUST also support clients passing an empty request body for this case.
Action Invocation Action parameter values are encoded in a single JSON object in the request body. Each non-binding parameter value is encoded as a separate name/value pair in this JSON object. The name is the name of the parameter. The value is the parameter value in the JSON representation appropriate for its type. Entity typed parameter values MAY include a subset of the properties, or just the , as appropriate to the action. Any parameter values not specified in the JSON object are assumed to have the null value. Example 44: { "param1": 42, "param2": { "Street": "One Microsoft Way", "Zip": }, "param3": [ 1, 42, 99 ], "param4": null } In order to invoke an action with no non-binding parameters, the client passes an empty JSON object in the body of the request. 4.01 Services MUST also support clients passing an empty request body for this case.
odata-json-format-v4.01-wd06-2018-10-19.docx