Forum Discussion
llittle
13 years agoNew Contributor
A little more information here. It appears there is a difference of behavior depending on how creates the association between property to be transferred. If I right click in the "association area" on the propertytransfer screen (where the xpath will appear) and select "get data" then associate the data from/to, an xpath is created but it looks very different and fails with the error previously stated. The xpath in this case looks liked this:
${FindProperty#Response#declare namespace prop='http://propertysearch.addresscorrection.intellireal.com/'; //prop:findPropertyResponse[1]/return[1]/address[1]/errorCode[1]}
If I instead click on the the icon to the right of the the area where the xpath information will get populated (looks like a stack of books icon), then make the appropriate associations for the data (from/to), the xpath looks like the following and does work. Seems like a defect to me.
declare namespace ns2='http://propertysearch.addresscorrection.intellireal.com/';
//ns2:findPropertyResponse[1]/return[1]/address[1]/errorCode[1]
${FindProperty#Response#declare namespace prop='http://propertysearch.addresscorrection.intellireal.com/'; //prop:findPropertyResponse[1]/return[1]/address[1]/errorCode[1]}
If I instead click on the the icon to the right of the the area where the xpath information will get populated (looks like a stack of books icon), then make the appropriate associations for the data (from/to), the xpath looks like the following and does work. Seems like a defect to me.
declare namespace ns2='http://propertysearch.addresscorrection.intellireal.com/';
//ns2:findPropertyResponse[1]/return[1]/address[1]/errorCode[1]