C4C Custom Field Mapping

With Release20/11, In Mind Cloud Digital Sales Platform (DSP) supports the custom business data attribute field (having range as String, Boolean and Decimal) mapping between DSP and C4C. It uses the LOOKUP Table to maintain the mapping.

There are two steps required to map the DSP custom BDA and C4C custom fields.

• Defining custom BDA having the range property within the supported data types and the domain with supported Subject Type.
• Mapping the DSP Custom BDA and C4C Custom Fields

Supported Graph Type and Subject Type

The following are supported GRAPH and SUBJECT types.

• Account (Graph Type)
  • Account (Subject Type)
  • Address (Subject Type)
  • PartnerRoleRecord (Subject Type)
• Contact (Graph Type)
  • Contact (Subject Type)
• Opportunity (Graph Type)
  • Opportunity (Subject Type)
• Quote (Graph Type)
  • SalesItem
  • PartnerFunctionRecord

Supported Data Types

The following are supported data type that can be used to define the range property of custom BDA.

• String
  • Syntax for defining range - <rdfs:range rdf:resource="&xsd;string"/>
• Boolean
  • Syntax for defining range - <rdfs:range rdf:resource="&xsd;boolean"/>
• Decimal
  • Syntax for defining range - <rdfs:range rdf:resource="&xsd;decimal"/>

The following are supported data type mapping between DSP and C4C.

Defining the Custom Field in DSP

The custom fields can be defined in DSP inside the application-schema-ext.owl file.

• Download the application-schema-ext
• Add the new custom BDA for supported domain with the following property
  • Type must be functional property
  • Domain must be defined within the supported domain/subject types URI
  • Sub property must be assertion
  • Range should be either string or decimal or boolean.
  • Upload the application-ext.owl to the system

The restart is necessary to refresh the newly added custom field in the system. The followings are the example of supported custom BDA definition for the Account business type.

<!-- http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountTextField -->

    <owl:DatatypeProperty rdf:about=" http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountTextField">

<rdf:type rdf:resource="&owl;FunctionalProperty"/>

             <rdfs:domain rdf:resource="&as;Account"/>

             <rdfs:subPropertyOf rdf:resource="&as;assertion"/>

             <rdfs:range rdf:resource="&xsd;string"/>

    </owl:DatatypeProperty>

<!-- http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountBooleanField -->




    <owl:DatatypeProperty rdf:about="&ase;zAccountBooleanField">

<rdf:type rdf:resource="&owl;FunctionalProperty"/>

             <rdfs:domain rdf:resource="&as;Account"/>

             <rdfs:subPropertyOf rdf:resource="&as;assertion"/>

             <rdfs:range rdf:resource="&xsd;boolean"/>

    </owl:DatatypeProperty>

<!-- http://www.inmindcloud.com/application/application-schema-ext.owl#zAccountDecimalField -->

    <owl:DatatypeProperty rdf:about="&ase;zAccountDecimalField">

<rdf:type rdf:resource="&owl;FunctionalProperty"/>

             <rdfs:domain rdf:resource="&as;Account"/>

             <rdfs:subPropertyOf rdf:resource="&as;assertion"/>

             <rdfs:range rdf:resource="&xsd;decimal "/>

    </owl:DatatypeProperty>

Mapping the DSP Custom BDA and C4C Custom Field

Once the supported custom BDA has been defined, the next step is to map the supported custom BDA with the custom field created in C4C by using the pre delivered LookupTable, called CUSTOM_CFC_FIELDS. The table contains the following fields.

• MX GRAPH TYPE URI
  • The supported PRIMRY Business Type URI. It must be full URI of Supported Graph Types available in DSP.

(Example Account, Contact, Opportunity, Quote)

• MX SUBJECT TYPE URI
  • The supported Subject Type URI. It must be full URI of Supported Subject Types available in DSP.

(Example Address, PartnerRoleRecord, SalesItem, PartnerFunctionRecord )

• MX FIELD URI
  • The custom BDA URI having the domain of supported SUBJECT TYPE URI and supported data type (such as String, Boolean, Decimal)
• CFC FIELD NAME
  • The custom field name defined in C4C
• CFC FIELD NAMESPAC
  • The name space of the field name generated by C4C while creating the new custom field. ( Example a00:zAccountHeaderText1 ).
• CFC XPATH
  • The XPath expression that can reach to the root level for the SUBJECT_TYPE. The XPath definition for each supported SUBJECT TYPE are fixed and it needs to follow the exact syntax. It will explain more details in individual import section.

The custom fields mapping can be defined in excel and uploaded to the DSP.

• Download the CUSTOM_CFC_FIELDS table to define the custom field mapping
• Define the mapping record
• Upload it back to the DSP

Uploading will notify if the DSP detected MX FIELD URI which cannot be found in the system due to wrong definition or the fact that server restarts is required. Therefore, it is recommended to define the DSP custom field in application-ext.owl first before defining the custom field mapping in the table.

Note: Custom BDA should be defined and available in the system first before uploading the CUSTOM_CFC_FIELDS table. If the DSP shows the notification saying MX Field URI Not Found, it means that the MX field URI defined in the excel was still not known in the system. It could be due to the fact that, the custom has not been defined or server restart needs to be done.