Create the path dynamically via the API createKey
from the ODataModel:
const path = myODataModel.createKey("/Products", {
ProductID: 999, // your dynamic key value
AnotherKeyProperty: "...",
});
myODataModel.update(path /*,...*/);
Compared to concatenating strings for the path manually, createKey
offers the following advantages:
- It outputs the key value always in the correct format corresponding to the EDM type of the given property (using
ODataUtils.formatValue
internally). E.g.: If ProductID
has the type Edm.Int64
, UI5 appends the character "l"
in the output string aligning with the OData specification: "999"
→ "999l"
- It makes sure that all keys are encoded according to the URI standard (using
encodeURIComponent
api internally). E.g.: ProductID='sp ace'
→ ProductID='sp%20ace'
- It outputs the key values always in the correct order no matter which backend system serves the metadata. Given the same metadata definition, it is possible that one system serves the metadata with keys in different orders than others. In such cases, if keys are just concatenated manually, the app would fail horribly throwing vague errors when it's transported to the system serving different key orders.
Note
Since createKey
relies on the information from the service metadata, the API should be performed after $metadata
is loaded. For this, the promise based API metadataLoaded
can be used.
myODataModel.metadataLoaded().then(/*createKey*/);
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…