Create Constituent Message

The "CreateConstituent" message is sent from the Global Partner (GP) to Global Ministry Center (GMC).

The message adds a new constituent from the GP to the GMC Source System database.

Once the sent "CreateConstituent" message has been processed by the GMC, a corresponding "ConstituentCreated" message will eventually be returned to the GP from the GMC. This is an asynchronous process).

Sample Message
Error Messages

Sample Message

Below is an example of a "CreateConstituent" message to with soap action of, traced through Fiddler. Please code to this example.

Areas highlighted in CYAN are added automatically by WCF for ws Federated security.
Areas highlighted in GREEN are added automatically by WCF.

Content-Type: application/soap+xml; charset=utf-8
Content-Length: 3267
Expect: 100-continue
Accept-Encoding: gzip, deflate
<s:Envelope xmlns:s="" xmlns:a="" xmlns:u="">
    <a:Action s:mustUnderstand="1"></a:Action>
    <SendersAppName xmlns="">

    <SendersName xmlns="">

    <SendersTrackingId xmlns="">[string]</SendersTrackingId>
    <a:To s:mustUnderstand="1"></a:To>
    <o:Security s:mustUnderstand="1" xmlns:o="">
      <u:Timestamp u:Id="_0">
      <SecurityContextToken u:Id="uuid-4bd33590-ab17-44ed-89b9-79dc8e8e472f-2" xmlns="">
      <Signature xmlns="">
          <CanonicalizationMethod Algorithm=""/>
          <SignatureMethod Algorithm=""/>
          <Reference URI="#_0">
              <Transform Algorithm=""/>
             <DigestMethod Algorithm=""/>
             <o:Reference URI="#uuid-4bd33590-ab17-44ed-89b9-79dc8e8e472f-2"/>

    <EsbEnvelope xmlns:xsi="" 

           <MessageType schemaLocation="">

           <CreateConstituent SchemaVersion ="1.0" xmlns="">





Name Description
EsbEnvelope Headers
SendersName Supplied by Cornerstone Connect during GP setup
SendersAppName Supplied by Cornerstone Connect during GP setup
SendersTrackingId Supplied by Cornerstone Connect during GP setup
ToAddress Supplied by Cornerstone Connect during GP setup
FromAddress Supplied by Cornerstone Connect during GP setup
RequestId Unique number created by GP in order to track specific messages. A message returned from Compass will have the RequestId populated in the RequestCorrelationId.
IP country code sending the message
ConstituentId New constituent id
Name Full name of the new constituent (required)
FirstName First name of the new constituent (optional)
LastName Last name of the new constituent (required)
TransactionDate Date the GP solidified the transaction. This can be the same day or earlier than the SentDate.
SentDate Automatically populated when the message is sent

Possible Error Messages Returned from the Compass Party Host

Error Message Text Error Message Description
PartnerCountryCode is required  
ConstituentId is required  
Name is required  
LastName is required  
TransactionDate is required
Unable to obtain db_id from DB table for code = {value} The PartnerCountryCode provided does not exist in the DB
LastModifiedUser ({value}) does not exist The user does not exist in the DB
LastModifiedUser ({value}) is not active The user is not active in the DB
ConstituentId (@con_id): {value} already exists The ConstituentId provided already exists in the DB
FirstName (@first_name): {value} exceeds 60 characters  
LastName (@last_name): {value} exceeds 60 characters  
Name (@name): {value} exceeds 60 characters
ConstituentId (@con_id): {value} cannot be larger than {value}  


New comments are not being accepted at this time.

Docs Navigation