cancel
Showing results for 
Search instead for 
Did you mean: 

FormattedAddress XML error when calling Query Accounts Webservice

0 Kudos

Hi,

i try to get back the address uuid from a specific customer by webservice in an HCI DS project.

I use GetCustomerbyIdentification -> Inbound Service Interface (public)

As long as im setting CustomerTransmissionRequestCode to '2' (complete node) and AddressInformationTransmissionRequestcode to '4' (exclude node) the job returns the Account UUID without any error. But i didn't get the Address UUID with this RequestReturn Setup. See Attached Response in Pic 2

When I try to set AddressInformationTransmissionRequestcode  also to '2' or even '1' (complete node) i always get the following error in View-design-data viewer and also on task run:

2015-10-27 20:30:01       (E)(8676:8692)     XML-240108      |Session __JOB_DSoD_JIT_QueryAccountsToSQL_1445977783239_176|Data flow __DF_DSoD_JIT_VIEWDATA_1445977783239_176_1|Transform FindbyIdentification-Function1

                                                               An element named <FormattedAddress> present in the XML data input does not exist in the XML format used to set up this XML

                                                               source in data flow <__DF_DSoD_JIT_VIEWDATA_1445977783239_176_1>. Validate your XML data.

2015-10-27 20:30:01       (E)(8676:8692)     XML-240307      |Session __JOB_DSoD_JIT_QueryAccountsToSQL_1445977783239_176|Data flow __DF_DSoD_JIT_VIEWDATA_1445977783239_176_1|Transform FindbyIdentification-Function1

                                                               XML parser failed: See previously displayed error message.

2015-10-27 20:30:11       (E)(8676:8780)     XML-240307      |Session __JOB_DSoD_JIT_QueryAccountsToSQL_1445977783239_176|Data flow __DF_DSoD_JIT_VIEWDATA_1445977783239_176_1|Transform FindbyIdentification-Function1

                                                               XML parser failed: See previously displayed error message.

The FormattedAddress node already exists in the wdsl response schema. See picture 1.

I don't know what causes the error or have another idea to get the address UUID.

Thank you,

Rene

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi,

Have you been able to resolve this issue? We have the same issue and would appreciate if you had any further updates on this.

Thanks,

Tejas.

RiccardoBrogi
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Rene,

were you able to solve this problem? I'm facing exactly the same error in DS.

BR,

Riccardo