CC&B - XAI Integration for Persons

Question

Good afternoon,
We are trying to develop an Inbound Service so that external systems can create Persons on CC&B.
We followed these steps to create and register the web service:
1. Used Schema Editor to create the schema and saved it to a XSD file. The Schema was based of the "Person" service.
2. Entered the application and created a new XAI Inbound Service, using the schema created.
3. Tested using XAI Dynamic Submission, XAI Submission and SOAP Sonar... All of them returned the same error message:
+<?xml version="1.0"; ?>+
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">+
+<soap:Body >+
+<soap:Fault >+
+<faultcode>soap:Client</faultcode>+
+<faultstring>Client Error</faultstring>+
+<detail>+
+<ResponseStatus>F</ResponseStatus>+
+<ResponseCode>2013</ResponseCode>+
+<ResponseText>Error while executing the request:+
com.splwg.shared.common.ApplicationError: (Server Message)
+     Category: 3+
+     Number: 253+
+     Call Sequence: ;CIPCPNMR;CIPCPNML;CIPCPERP+
+     Program Name: CIPCPERP+
+     Text: Name field missing+
+     Description: A mandatory field has been left blank. Please enter a value and retry your request.+
+     Table:+
+     Field: </ResponseText>+
+<ResponseData text="Name field missing" category="3" numParm="1" parm1="Name" number="253" />+
+</detail>+
+</soap:Fault>+
+</soap:Body >+
+</soap:Envelope>+
The error message shows that A mandatory field - "Name" - has been left blank, but does not show which table or field is missing.
Furthermore, while re checking the XML sent and the WSDL, there is no field "Name" which is not being sent on the Request...
We would appreciate any suggestions to debug and overtake this problem.
Best regards,
Pedro Malheiro

Answer 1

A bit tricky to resolve, but the problem is that the schema definitions are old. This has been discussed in previous threads as well.
It still boils down to which CC&B Version and which xmlMetaInfo or Schema Editor Version.
In CC&B 2.2 there is redundant definition of "Name" attribute under element "PersonNamesRow" for ENTITY_NAME and ENTITY_NAME_UPR:
<xsd:attribute name="Name">
     <xsd:annotation>
          <xsd:appinfo>
               <xsd:has-property name="uniqueId" value="ENTITY_NAME"/>
               <xsd:has-property name="dataType" value="string"/>
          </xsd:appinfo>
     </xsd:annotation>
     <xsd:simpleType>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="150"/>
          </xsd:restriction>
     </xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="Name">
     <xsd:annotation>
          <xsd:appinfo>
               <xsd:has-property name="uniqueId" value="ENTITY_NAME_UPR"/>
               <xsd:has-property name="dataType" value="string"/>
          </xsd:appinfo>
     </xsd:annotation>
     <xsd:simpleType>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="64"/>
          </xsd:restriction>
     </xsd:simpleType>
</xsd:attribute>You need to rename the latter "Name" attribute for ENTITY_NAME_UPR to something like "UpperName" and it'll work:
<xsd:attribute name="UpperName">
     <xsd:annotation>
          <xsd:appinfo>
               <xsd:has-property name="uniqueId" value="ENTITY_NAME_UPR"/>
               <xsd:has-property name="dataType" value="string"/>
          </xsd:appinfo>
     </xsd:annotation>
     <xsd:simpleType>
          <xsd:restriction base="xsd:string">
               <xsd:maxLength value="64"/>
          </xsd:restriction>
     </xsd:simpleType>
</xsd:attribute>