Profile Fields in REST

Former Member — Wed, 05 Aug 2020 21:54:51 GMT

Current Revision posted to Developer Training by Former Member on 08/05/2020 21:54:51

Profile Fields can be set and retrieved in REST as in any other of Verint Community's API spaces.

General Notes on Profile Fields

To set a profile field, you must first define the profile field in Administration > Membership > Profile Fields and provide a value that is a valid data type for the defined field.

Using Profile Fields in REST

When building your REST request, you can include as many Profile Fields as you desire in the form with the following syntax:

_ProfileFields_<FieldName>="<FieldValue>"

Also note the following related bahaviors:

Providing a <FieldName> that does not exist will not save the Profile Field, because no matching Profile Field has been defined in Administration.
Setting <FieldValue> to an empty string ("") for an existing <FieldName> for a user will delete the matching User Profile Field.
Providing a different <FieldValue> for an existing <FieldName> for a user will overwrite the existing User Profile Field value.

Tags: profile fields, REST

Profile Fields in REST

Former Member — Wed, 05 Aug 2020 21:51:22 GMT

Revision 2 posted to Developer Training by Former Member on 08/05/2020 21:51:22

Profile Fields can be set and retrieved in REST as in any other of Verint Community's API spaces.

General Notes on Profile Fields

To set a profile field, you must first define the profile field in Administration > Membership > Profile Fields and provide a value that is a valid data type for the defined field.

Extended Attributes are extensible, meaning they are perfectly upgrade safe in terms of storage/retrieval syntax. There are no plans to deprecate or obsolete them. However, it is strongly recommended that any robust custom functionality implementation (e.g., anything that requires filtering or searching) should consider using a custom data store and access methods instead of relying on Extended Attributes.

Using Profile Fields in REST

When building your REST request, you can include as many Profile Fields as you desire in the form with the following syntax:

_ProfileFields_<FieldName>="<FieldValue>"

Also note the following related bahaviors:

Providing a <FieldName> that does not exist will not save the Profile Field, because no matching Profile Field has been defined in Administration.
Setting <FieldValue> to an empty string ("") for an existing <FieldName> for a user will delete the matching User Profile Field.
Providing a different <FieldValue> for an existing <FieldName> for a user will overwrite the existing User Profile Field value.

Tags: profile fields, REST

Profile Fields in REST

Former Member — Wed, 05 Aug 2020 21:51:03 GMT

Revision 1 posted to Developer Training by Former Member on 08/05/2020 21:51:03

Profile Fields can be set and retrieved in REST as in any other of Verint Community's API spaces.

General Notes on Profile Fields

To set a profile field, you must first define the profile field in Administration > Membership > Profile Fields and provide a value that is a valid data type for the defined field.

Using Profile Fields in REST

When building your REST request, you can include as many Profile Fields as you desire in the form with the following syntax:

_ProfileFields_<FieldName>="<FieldValue>"

Also note the following related bahaviors:

Providing a <FieldName> that does not exist will not save the Profile Field, because no matching Profile Field has been defined in Administration.
Setting <FieldValue> to an empty string ("") for an existing <FieldName> for a user will delete the matching User Profile Field.
Providing a different <FieldValue> for an existing <FieldName> for a user will overwrite the existing User Profile Field value.