Topic
  • 3 replies
  • Latest Post - ‏2012-07-27T13:21:23Z by SystemAdmin
SystemAdmin
SystemAdmin
345 Posts

Pinned topic Response XML does nto contain the data added into MDM for the request XML.

‏2012-07-26T09:44:28Z |
Hi,
We created an extension in MDMv10.0, it was working and we were able to get the response with extended object for Txs. Then we created some code tables, after this response XML we got has no elements and values for the BObjs but data was added into MDM. And also we are not getting the response for the OTB transactions.

PFA response XML.
Let me know if i need to do some configuration change.

Please reply any knows or come across this issue.
Thanks in advance.

Regards,
Ravi(BVBian)
Updated on 2012-07-27T13:21:23Z at 2012-07-27T13:21:23Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    345 Posts

    Re: Response XML does nto contain the data added into MDM for the request XML.

    ‏2012-07-26T15:41:04Z  
    Hi,

    The problem is that the server was unable to parse the response xsd or the response xsd did not define the data elements that needed to go in the response.

    In v10, we changed how the XSDs were organized so you can use MDMDomains.xsd as the request and response schema for all messages. Your response XML is referencing CustomDomainResponse.xsd, which is correct if you are intending to use the older style of separate request and response XSDs.

    Make sure that CustomDomainResponse.xsd does not have any validation errors - this can happen if the file redefines elements that are already defined in another XSD. Since you defined code tables, most likely it is an element in a code table BObj that is causing the problem (this would only affect responses, because the request XSD does not include code table fields).

    If you can find which element declaration is a duplicate, you can just delete it from CustomDomainResponse.xsd.

    Hope that helps, Catherine.
  • SystemAdmin
    SystemAdmin
    345 Posts

    Re: Response XML does nto contain the data added into MDM for the request XML.

    ‏2012-07-27T10:59:58Z  
    Hi,

    The problem is that the server was unable to parse the response xsd or the response xsd did not define the data elements that needed to go in the response.

    In v10, we changed how the XSDs were organized so you can use MDMDomains.xsd as the request and response schema for all messages. Your response XML is referencing CustomDomainResponse.xsd, which is correct if you are intending to use the older style of separate request and response XSDs.

    Make sure that CustomDomainResponse.xsd does not have any validation errors - this can happen if the file redefines elements that are already defined in another XSD. Since you defined code tables, most likely it is an element in a code table BObj that is causing the problem (this would only affect responses, because the request XSD does not include code table fields).

    If you can find which element declaration is a duplicate, you can just delete it from CustomDomainResponse.xsd.

    Hope that helps, Catherine.
    Thanks Catherine for the reply. We are able to get the response with all the elements and values.

    For code tables tool generated DWLCommonResponse_extension.xsd.snippet which will be merged to DWLCommonResponse_extension.xsd. We removed snippet merged in DWLCommonResponse_extension.xsd, then it worked.

    My question is why in the first place it merged when it is really not required.
    Regards,
    Ravi
  • SystemAdmin
    SystemAdmin
    345 Posts

    Re: Response XML does nto contain the data added into MDM for the request XML.

    ‏2012-07-27T13:21:23Z  
    Thanks Catherine for the reply. We are able to get the response with all the elements and values.

    For code tables tool generated DWLCommonResponse_extension.xsd.snippet which will be merged to DWLCommonResponse_extension.xsd. We removed snippet merged in DWLCommonResponse_extension.xsd, then it worked.

    My question is why in the first place it merged when it is really not required.
    Regards,
    Ravi
    Hi,

    The XML for the code table BObjs are required in the response XSD to support querying the code table values using getAllCodeTypes and similar transactions.

    Normally, merging in the code table XSD content shouldn't cause a problem. There may just be one element definition which is causing an error. For the newer style of XSD I believe the workbench checks for duplicate element declarations on merge to avoid this problem.

    Thanks, Catherine.