User Interfaces Release 9.1 Subscriber Provisioning Reference Manual 404 — If subscriber, field name, or field and value combination does not exist MSR4001 is returned if the subscriber is not found. MSR4002 is returned if the field is not found. MSR4053 is returned if the value does not match. Example 1 GET {baseURI}/msr/sub/MSISDN/+33123654862/field/ AccountId/10404723525 10404723525 Example 2 GET {baseURI}/msr/sub/MSISDN/+33123654862/field/BillingDay/1 1 Example 3 GET {baseURI}/msr/sub/MSISDN/+33123654862/field/ Entitlement/DayPass;HighSpeedData Note: The semicolon between the entitlement values may need to be encoded as %3B for certain clients.
DayPass HighSpeedData For a request where the presence of multiple values is requested, a match is considered to have been made if the requested values form a subset of the values stored in the profile. That is, if all of the values requested exist in the profile, return success, regardless of how many other values may exist in the profile. If any or all of the values are not present as part of the profile, 404 with MSR4053 is returned. Set Field Value operation Description This operation sets a field to the specified value for the subscriber identified by the specified key name and key value.
This operation replaces ("sets") the value of the field, which means that any existing values for the field are deleted first. For multi-value fields, all previous values are erased and the new specified set is inserted. Adding values to a current set is accomplished by using the Add Field Value operation. All fields (including multi-value fields) of a subscriber or pool profile that can be modified in a single-field request can also be modified in a multiple-fields request. All fields and all values must be valid to complete the update. Using a multiple-fields request returns only one Sh notification per update request. 53 910-6701-001 Revision A, June 2013