ADDPROFILEKEY()`¶

About AddProfileKey¶

Associates a new key value with a specific profile, such as a Contact Record ContactId.

A profile object can have a single unique key and any number of additional keys that can be used to identify the profile that it belongs to.

Method Signature¶

METHODS /AWS1/IF_CUS~ADDPROFILEKEY
  IMPORTING
    !IV_PROFILEID TYPE /AWS1/CUSUUID OPTIONAL
    !IV_KEYNAME TYPE /AWS1/CUSNAME OPTIONAL
    !IT_VALUES TYPE /AWS1/CL_CUSREQUESTVALUELIST_W=>TT_REQUESTVALUELIST OPTIONAL
    !IV_DOMAINNAME TYPE /AWS1/CUSNAME OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_cusaddprofilekeyrsp
  RAISING
    /AWS1/CX_CUSACCESSDENIEDEX
    /AWS1/CX_CUSBADREQUESTEX
    /AWS1/CX_CUSINTERNALSERVEREX
    /AWS1/CX_CUSRESOURCENOTFOUNDEX
    /AWS1/CX_CUSTHROTTLINGEX
    /AWS1/CX_CUSCLIENTEXC
    /AWS1/CX_CUSSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_profileid` `TYPE /AWS1/CUSUUID` `/AWS1/CUSUUID`¶

The unique identifier of a customer profile.

`iv_keyname` `TYPE /AWS1/CUSNAME` `/AWS1/CUSNAME`¶

A searchable identifier of a customer profile. The predefined keys you can use include: _account, _profileId, _assetId, _caseId, _orderId, _fullName, _phone, _email, _ctrContactId, _marketoLeadId, _salesforceAccountId, _salesforceContactId, _salesforceAssetId, _zendeskUserId, _zendeskExternalId, _zendeskTicketId, _serviceNowSystemId, _serviceNowIncidentId, _segmentUserId, _shopifyCustomerId, _shopifyOrderId.

`it_values` `TYPE /AWS1/CL_CUSREQUESTVALUELIST_W=>TT_REQUESTVALUELIST` `TT_REQUESTVALUELIST`¶

A list of key values.

`iv_domainname` `TYPE /AWS1/CUSNAME` `/AWS1/CUSNAME`¶

The unique name of the domain.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_cusaddprofilekeyrsp` `/AWS1/CL_CUSADDPROFILEKEYRSP`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->addprofilekey(
  it_values = VALUE /aws1/cl_cusrequestvaluelist_w=>tt_requestvaluelist(
    ( new /aws1/cl_cusrequestvaluelist_w( |string| ) )
  )
  iv_domainname = |string|
  iv_keyname = |string|
  iv_profileid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_name = lo_result->get_keyname( ).
  LOOP AT lo_result->get_values( ) into lo_row.
    lo_row_1 = lo_row.
    IF lo_row_1 IS NOT INITIAL.
      lv_string1to255 = lo_row_1->get_value( ).
    ENDIF.
  ENDLOOP.
ENDIF.

/AWS1/IF_CUS=>ADDPROFILEKEY()¶