Thanks for mentioning a bit about StaticName. This put an end to my misery.
It would seem that for simple fields that are not MMS-related, for example Title, the syntax of lazy updating is allowed. For example, based on it, the next update is processed without errors.
<Field Name="Title">Some Title</Field>
However, the rules do not match for MMS-related rules. Following the above approach, I went to my MMS fields. This type of field can be updated with arbitrary values ββif you identify it by a friendly name and enter an integer, for example:
<Field Name="Activity">20</Field>
"20" just translates into some term.
I tried many numbers and they all came back as the same term.
Alternatively, if I approach the documented way of updating the value, while identifying the field with "Activity", the service returns error 0x80020005.
<Field Name="Activity">HTA|fe951639-7c90-41ee-9888-6ae0e6523120</Field>
So donβt do it. Only when the moons are fully aligned do I find success. A static name is key .
<Field Name="j06a8d8240f84aec987f6a28effa3ae1">HTA|fe951639-7c90-41ee-9888-6ae0e6523120</Field>
Another way to search for StaticName is to search for field type = "Note" for each MMS field in response to a GetList request. This operation takes less than 1 input than GetListContentType. You only need the list name, not the contentTypeID.
Rock on.
catBus
source share