Utilizing Distinguished Field
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > BizTalk Server > BizTalk Server Orchestration > Utilizing Distinguished Field




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Utilizing Distinguished Field  
Ellen Deak


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-07-06 12:19 AM

Hello,

I'm having trouble accessing the value of a distinguished field in an
orchestration. If anyone can help identify what I'm doing wrong, I would
really appreciate it.

I have a schema generated from an adapter. I've promoted one of the elements
in that schema as a Distinguished Field.

After doing the send/receive to the adapter port in my orchestration, I have
a decision shape where I am attempting to to check this distinguished field
and do some different processing based on its value.

However, the decision always seems to evaluate as if the value is blank.
I've written the returned message out to a file and can see that the field
does have a value (sample at end of this posting). I've written the
distinguished field out to the event log and it seems to be blank.

The following is the expression for the decision

autocashItemXrefMBFSoapOut.bodyPart.jdeResponse.callMethod.params.cEdiSucces
sfullyProcess == "1"

The following is the expression for writing to the event log

System.Diagnostics.EventLog.WriteEntry("Debug","params.cEdiSuccessfullyProce
ss="+autocashItemXrefMBFSoapOut.bodyPart.jdeResponse.callMethod.params.cEdiS
uccessfullyProcess);

The "else" side of the decision executes, even though the value in the
message is "1".

This is what I get in the event log:

params.cEdiSuccessfullyProcess=

Which is telling me the distinguished field is blank.

I'm pretty new to BizTalk and assume I must be missing something that I need
to do to access the distinguished field value. Any help would be appreciated
.

Thanks,
--
Ellen Deak
BizTalk 2004


<?xml version="1.0" encoding="utf-8"?><AutocashItemXrefMBFResponse
xmlns="http://iwaysoftware.com/exposed/services/JDE_N5503B01/AutocashItemXre
fMBF"><jdeResponse
user="BTSSERVICE" sessionidle="" type="callmethod"
session="8322.1149628469.45" environment="WDV7333" xmlns=""><callMethod
returnNullData="yes" name="AutocashItemXrefMBF" runOnError="yes"><returnCode
code="0" />
<params>
<cActionCode>A</cActionCode>
<szIdentifier2ndItem>19</szIdentifier2ndItem>
<szItemNoCustomerVendor>s</szItemNoCustomerVendor>
<szCostCenter>      111000</szCostCenter>
<szUserReservedCode />
<mnUserReservedNumber>0</mnUserReservedNumber>
<mnUserReservedAmount>0</mnUserReservedAmount>
<szUserReservedReference /><jdUserReservedDate />
<szUserId>BTSSERVICE</szUserId>
<szProgramId />
<szWorkStationId>AS01DEV</szWorkStationId>
<jdDateUpdated>2006/06/06</jdDateUpdated>
<mnTimeOfDay>161430</mnTimeOfDay>
<cEdiSuccessfullyProcess>1</cEdiSuccessfullyProcess>
</params></callMethod></jdeResponse></AutocashItemXrefMBFResponse>





[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Greg Forsythe


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-07-06 12:19 AM

What pipeline are you using to receive this message?
You will need a pipeline with the XmlDisassembler component
The standard XmlReceive pipeline has this component.
The XmlDisassembler identifies the Xml schema. The schema is where the
distinguished fields are defined. It then writes the distinguished fields
values into the message context where they are available inside your
orchestartion.

Greg

"Ellen Deak" <ellen@newsgroups.nospam> wrote in message
news:B009EC18-9DFF-47B2-A94B-338D51C8580A@microsoft.com...
> Hello,
>
> I'm having trouble accessing the value of a distinguished field in an
> orchestration. If anyone can help identify what I'm doing wrong, I would
> really appreciate it.
>
> I have a schema generated from an adapter. I've promoted one of the
> elements
> in that schema as a Distinguished Field.
>
> After doing the send/receive to the adapter port in my orchestration, I
> have
> a decision shape where I am attempting to to check this distinguished
> field
> and do some different processing based on its value.
>
> However, the decision always seems to evaluate as if the value is blank.
> I've written the returned message out to a file and can see that the field
> does have a value (sample at end of this posting). I've written the
> distinguished field out to the event log and it seems to be blank.
>
> The following is the expression for the decision
>
> autocashItemXrefMBFSoapOut.bodyPart.jdeResponse.callMethod.params.cEdiSucc
essfullyProcess
> == "1"
>
> The following is the expression for writing to the event log
>
> System.Diagnostics.EventLog.WriteEntry("Debug","params.cEdiSuccessfullyPro
cess="+autocashItemXrefMBFSoapOut.bodyPart.jdeResponse.callMethod.params.cEd
iSuccessfullyProcess);
>
> The "else" side of the decision executes, even though the value in the
> message is "1".
>
> This is what I get in the event log:
>
> params.cEdiSuccessfullyProcess=
>
> Which is telling me the distinguished field is blank.
>
> I'm pretty new to BizTalk and assume I must be missing something that I
> need
> to do to access the distinguished field value. Any help would be
> appreciated.
>
> Thanks,
> --
> Ellen Deak
> BizTalk 2004
>
>
> <?xml version="1.0" encoding="utf-8"?><AutocashItemXrefMBFResponse
> xmlns="http://iwaysoftware.com/exposed/services/JDE_N5503B01/AutocashItemX
refMBF"><jdeResponse
> user="BTSSERVICE" sessionidle="" type="callmethod"
> session="8322.1149628469.45" environment="WDV7333" xmlns=""><callMethod
> returnNullData="yes" name="AutocashItemXrefMBF"
> runOnError="yes"><returnCode
> code="0" />
> <params>
> <cActionCode>A</cActionCode>
> <szIdentifier2ndItem>19</szIdentifier2ndItem>
> <szItemNoCustomerVendor>s</szItemNoCustomerVendor>
> <szCostCenter>      111000</szCostCenter>
> <szUserReservedCode />
> <mnUserReservedNumber>0</mnUserReservedNumber>
> <mnUserReservedAmount>0</mnUserReservedAmount>
> <szUserReservedReference /><jdUserReservedDate />
> <szUserId>BTSSERVICE</szUserId>
> <szProgramId />
> <szWorkStationId>AS01DEV</szWorkStationId>
> <jdDateUpdated>2006/06/06</jdDateUpdated>
> <mnTimeOfDay>161430</mnTimeOfDay>
> <cEdiSuccessfullyProcess>1</cEdiSuccessfullyProcess>
> </params></callMethod></jdeResponse></AutocashItemXrefMBFResponse>







[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Ellen Deak


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-07-06 06:18 PM

I'm using the standard XMLReceive on the port.
--
Ellen Deak


"Greg Forsythe" wrote:

> What pipeline are you using to receive this message?
> You will need a pipeline with the XmlDisassembler component
> The standard XmlReceive pipeline has this component.
> The XmlDisassembler identifies the Xml schema. The schema is where the
> distinguished fields are defined. It then writes the distinguished fields
> values into the message context where they are available inside your
> orchestartion.
>
> Greg
>
> "Ellen Deak" <ellen@newsgroups.nospam> wrote in message
> news:B009EC18-9DFF-47B2-A94B-338D51C8580A@microsoft.com... 
>
>
>





[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Greg Forsythe


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-08-06 12:19 PM

Any chance of seeing the schema for this xml instance.
What type of adapter are you using?
Is the XLANG message a multi-part message?

Greg


"Ellen Deak" <ellen@newsgroups.nospam> wrote in message
news:A22BE9FE-72A9-436A-AB64-1C906CE0F171@microsoft.com...[vbcol=seagreen]
> I'm using the standard XMLReceive on the port.
> --
> Ellen Deak
>
>
> "Greg Forsythe" wrote:
> 







[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Ellen Deak


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-08-06 06:19 PM

1.  The schema is lengthy so I put it at then end of this reply
2.  I am using iWay's JDE adapter
3.  Yes, Here's what they look like.

Multi-part Message Types
AutocashItemXrefMBFSoapIn
bodyPart			(AutocashItemXrefMBF node in schema)
AutocashItemXrefMBFSoapOut
bodyPart			(AutocashITemXrefMBFResponse node in schema)

Message
 autocashItemXrefMBFSoapOut		(AutocashIte
mXrefMBFSoapOut)

Thanks for taking the time to help me out,

Ellen Deak

---------------------------
auto generated schema

<?xml version="1.0" encoding="utf-16" ?>
- <xs:schema
xmlns:tns="http://iwaysoftware.com/exposed/services/JDE_N5503B01/AutocashIte
mXrefMBF"
xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
elementFormDefault="qualified"
targetNamespace="http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF" xmlns:xs="http://www.w3.org/2001/XMLSchema">
- <xs:element name="AutocashItemXrefMBF">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="jdeRequest">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="callMethod">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="params">
- <xs:complexType>
- <xs:sequence>
<xs:element minOccurs="0" name="cActionCode" type="xs:string" />
<xs:element minOccurs="0" name="szIdentifier2ndItem" type="xs:string" />
<xs:element minOccurs="0" name="szItemNoCustomerVendor" type="xs:string" />
<xs:element minOccurs="0" name="szCostCenter" type="xs:string" />
<xs:element minOccurs="0" name="szUserReservedCode" type="xs:string" />
<xs:element minOccurs="0" name="mnUserReservedNumber" type="xs:string" />
<xs:element minOccurs="0" name="mnUserReservedAmount" type="xs:string" />
<xs:element minOccurs="0" name="szUserReservedReference" type="xs:string"
/>
<xs:element minOccurs="0" name="jdUserReservedDate" type="xs:string" />
<xs:element minOccurs="0" name="szUserId" type="xs:string" />
<xs:element minOccurs="0" name="szProgramId" type="xs:string" />
<xs:element minOccurs="0" name="szWorkStationId" type="xs:string" />
<xs:element minOccurs="0" name="jdDateUpdated" type="xs:string" />
<xs:element minOccurs="0" name="mnTimeOfDay" type="xs:string" />
<xs:element minOccurs="0" name="cEdiSuccessfullyProcess" type="xs:string"
/>
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:element minOccurs="0" name="onError">
- <xs:complexType>
- <xs:sequence>
<xs:any minOccurs="0" />
</xs:sequence>
- <xs:attribute name="abort" use="required">
- <xs:simpleType>
- <xs:restriction base="xs:string">
<xs:enumeration value="yes" />
<xs:enumeration value="no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
- <xs:attribute name="name" use="required">
- <xs:simpleType>
- <xs:restriction base="xs:string">
<xs:enumeration value="AutocashItemXrefMBF" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="app" type="xs:string" use="optional" />
- <xs:attribute name="runOnError" use="optional">
- <xs:simpleType>
- <xs:restriction base="xs:string">
<xs:enumeration value="yes" />
<xs:enumeration value="no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
- <xs:attribute name="returnNullData" use="optional">
- <xs:simpleType>
- <xs:restriction base="xs:string">
<xs:enumeration value="yes" />
<xs:enumeration value="no" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="trans" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
</xs:sequence>
- <xs:attribute name="type" use="required">
- <xs:simpleType>
- <xs:restriction base="xs:string">
<xs:enumeration value="callmethod" />
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="session" type="xs:string" use="optional" />
<xs:attribute name="sessionidle" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:element name="AutocashItemXrefMBFResponse">
- <xs:annotation>
- <xs:appinfo>
- <properties xmlns="http://schemas.microsoft.com/BizTalk/2003">
<property distinguished="true"
xpath="/*[local-name()='AutocashItemXrefMBFResponse' and
namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF']/*[local-name()='jdeResponse'
and
namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF']/*[local-name()='callMethod'
and
namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF']/*[local-name()='params'
and
namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF']/*[local-name()='cEdiSuccessfullyProcess'
and
namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Autoc
ashItemXrefMBF']" />
</properties>
</xs:appinfo>
</xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:element name="jdeResponse">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="callMethod">
- <xs:complexType>
- <xs:sequence>
- <xs:element name="returnCode">
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
<xs:attribute name="code" type="xs:string" use="required" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
- <xs:element minOccurs="0" name="errors">
- <xs:complexType>
- <xs:sequence>
- <xs:element maxOccurs="unbounded" name="error">
- <xs:complexType>
- <xs:simpleContent>
- <xs:extension base="xs:string">
<xs:attribute name="code" type="xs:string" use="optional" />
<xs:attribute name="name" type="xs:string" use="optional" />
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:element name="params">
- <xs:complexType>
- <xs:sequence>
<xs:element minOccurs="0" name="cActionCode" type="xs:string" />
<xs:element minOccurs="0" name="szIdentifier2ndItem" type="xs:string" />
<xs:element minOccurs="0" name="szItemNoCustomerVendor" type="xs:string" />
<xs:element minOccurs="0" name="szCostCenter" type="xs:string" />
<xs:element minOccurs="0" name="szUserReservedCode" type="xs:string" />
<xs:element minOccurs="0" name="mnUserReservedNumber" type="xs:string" />
<xs:element minOccurs="0" name="mnUserReservedAmount" type="xs:string" />
<xs:element minOccurs="0" name="szUserReservedReference" type="xs:string"
/>
<xs:element minOccurs="0" name="jdUserReservedDate" type="xs:string" />
<xs:element minOccurs="0" name="szUserId" type="xs:string" />
<xs:element minOccurs="0" name="szProgramId" type="xs:string" />
<xs:element minOccurs="0" name="szWorkStationId" type="xs:string" />
<xs:element minOccurs="0" name="jdDateUpdated" type="xs:string" />
<xs:element minOccurs="0" name="mnTimeOfDay" type="xs:string" />
<xs:element minOccurs="0" name="cEdiSuccessfullyProcess" type="xs:string"
/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute fixed="AutocashItemXrefMBF" name="name" type="xs:string" />
<xs:attribute name="app" type="xs:string" use="optional" />
<xs:attribute name="returnNullData" type="xs:string" use="optional" />
<xs:attribute name="runOnError" type="xs:string" use="optional" />
<xs:attribute name="trans" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute fixed="callmethod" name="type" type="xs:string" />
<xs:attribute name="user" type="xs:string" use="optional" />
<xs:attribute name="role" type="xs:string" use="optional" />
<xs:attribute name="session" type="xs:string" use="optional" />
<xs:attribute name="sessionidle" type="xs:string" use="optional" />
<xs:attribute name="environment" type="xs:string" use="optional" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>





[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Greg Forsythe


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-09-06 12:17 AM

Ellen,
The syntax for accessing a distinguished field is normally
Message.DistinguishedField
or in your case with multipart messages
AutocashItemXrefMBFSoapOut.bodyPart.cEdiSuccessfullyProcess

Normally intellisense will provide the distinguished field when you type the
dot after the message type.

Greg


"Ellen Deak" <ellen@newsgroups.nospam> wrote in message
news:4B4CFB5B-1876-45A1-8E4D-E24BC19EE3DE@microsoft.com...
> 1.  The schema is lengthy so I put it at then end of this reply
> 2.  I am using iWay's JDE adapter
> 3.  Yes, Here's what they look like.
>
> Multi-part Message Types
>    AutocashItemXrefMBFSoapIn
>        bodyPart (AutocashItemXrefMBF node in schema)
>    AutocashItemXrefMBFSoapOut
>        bodyPart (AutocashITemXrefMBFResponse node in schema)
>
> Message
>    autocashItemXrefMBFSoapOut (AutocashItemXrefMBFSoapOut)
>
> Thanks for taking the time to help me out,
>
> Ellen Deak
>
> ---------------------------
> auto generated schema
>
> <?xml version="1.0" encoding="utf-16" ?>
> - <xs:schema
> xmlns:tns="http://iwaysoftware.com/exposed/services/JDE_N5503B01/AutocashI
temXrefMBF"
> xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
> elementFormDefault="qualified"
> targetNamespace="http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> - <xs:element name="AutocashItemXrefMBF">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="jdeRequest">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="callMethod">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="params">
> - <xs:complexType>
> - <xs:sequence>
>  <xs:element minOccurs="0" name="cActionCode" type="xs:string" />
>  <xs:element minOccurs="0" name="szIdentifier2ndItem" type="xs:string" />
>  <xs:element minOccurs="0" name="szItemNoCustomerVendor" type="xs:string"
> />
>  <xs:element minOccurs="0" name="szCostCenter" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserReservedCode" type="xs:string" />
>  <xs:element minOccurs="0" name="mnUserReservedNumber" type="xs:string" />
>  <xs:element minOccurs="0" name="mnUserReservedAmount" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserReservedReference" type="xs:string"
> />
>  <xs:element minOccurs="0" name="jdUserReservedDate" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserId" type="xs:string" />
>  <xs:element minOccurs="0" name="szProgramId" type="xs:string" />
>  <xs:element minOccurs="0" name="szWorkStationId" type="xs:string" />
>  <xs:element minOccurs="0" name="jdDateUpdated" type="xs:string" />
>  <xs:element minOccurs="0" name="mnTimeOfDay" type="xs:string" />
>  <xs:element minOccurs="0" name="cEdiSuccessfullyProcess" type="xs:string"
> />
>  </xs:sequence>
>  </xs:complexType>
>  </xs:element>
> - <xs:element minOccurs="0" name="onError">
> - <xs:complexType>
> - <xs:sequence>
>  <xs:any minOccurs="0" />
>  </xs:sequence>
> - <xs:attribute name="abort" use="required">
> - <xs:simpleType>
> - <xs:restriction base="xs:string">
>  <xs:enumeration value="yes" />
>  <xs:enumeration value="no" />
>  </xs:restriction>
>  </xs:simpleType>
>  </xs:attribute>
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
> - <xs:attribute name="name" use="required">
> - <xs:simpleType>
> - <xs:restriction base="xs:string">
>  <xs:enumeration value="AutocashItemXrefMBF" />
>  </xs:restriction>
>  </xs:simpleType>
>  </xs:attribute>
>  <xs:attribute name="app" type="xs:string" use="optional" />
> - <xs:attribute name="runOnError" use="optional">
> - <xs:simpleType>
> - <xs:restriction base="xs:string">
>  <xs:enumeration value="yes" />
>  <xs:enumeration value="no" />
>  </xs:restriction>
>  </xs:simpleType>
>  </xs:attribute>
> - <xs:attribute name="returnNullData" use="optional">
> - <xs:simpleType>
> - <xs:restriction base="xs:string">
>  <xs:enumeration value="yes" />
>  <xs:enumeration value="no" />
>  </xs:restriction>
>  </xs:simpleType>
>  </xs:attribute>
>  <xs:attribute name="trans" type="xs:string" use="optional" />
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
> - <xs:attribute name="type" use="required">
> - <xs:simpleType>
> - <xs:restriction base="xs:string">
>  <xs:enumeration value="callmethod" />
>  </xs:restriction>
>  </xs:simpleType>
>  </xs:attribute>
>  <xs:attribute name="session" type="xs:string" use="optional" />
>  <xs:attribute name="sessionidle" type="xs:string" use="optional" />
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
>  </xs:complexType>
>  </xs:element>
> - <xs:element name="AutocashItemXrefMBFResponse">
> - <xs:annotation>
> - <xs:appinfo>
> - <properties xmlns="http://schemas.microsoft.com/BizTalk/2003">
>  <property distinguished="true"
> xpath="/*[local-name()='AutocashItemXrefMBFResponse' and
> namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF']/*[local-name()='jdeResponse'
> and
> namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF']/*[local-name()='callMethod'
> and
> namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF']/*[local-name()='params'
> and
> namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF']/*[local-name()='cEdiSuccessfullyProcess'
> and
> namespace-uri()='http://iwaysoftware.com/exposed/services/JDE_N5503B01/Aut
ocashItemXrefMBF']"
> />
>  </properties>
>  </xs:appinfo>
>  </xs:annotation>
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="jdeResponse">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="callMethod">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element name="returnCode">
> - <xs:complexType>
> - <xs:simpleContent>
> - <xs:extension base="xs:string">
>  <xs:attribute name="code" type="xs:string" use="required" />
>  </xs:extension>
>  </xs:simpleContent>
>  </xs:complexType>
>  </xs:element>
> - <xs:element minOccurs="0" name="errors">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element maxOccurs="unbounded" name="error">
> - <xs:complexType>
> - <xs:simpleContent>
> - <xs:extension base="xs:string">
>  <xs:attribute name="code" type="xs:string" use="optional" />
>  <xs:attribute name="name" type="xs:string" use="optional" />
>  </xs:extension>
>  </xs:simpleContent>
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
>  </xs:complexType>
>  </xs:element>
> - <xs:element name="params">
> - <xs:complexType>
> - <xs:sequence>
>  <xs:element minOccurs="0" name="cActionCode" type="xs:string" />
>  <xs:element minOccurs="0" name="szIdentifier2ndItem" type="xs:string" />
>  <xs:element minOccurs="0" name="szItemNoCustomerVendor" type="xs:string"
> />
>  <xs:element minOccurs="0" name="szCostCenter" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserReservedCode" type="xs:string" />
>  <xs:element minOccurs="0" name="mnUserReservedNumber" type="xs:string" />
>  <xs:element minOccurs="0" name="mnUserReservedAmount" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserReservedReference" type="xs:string"
> />
>  <xs:element minOccurs="0" name="jdUserReservedDate" type="xs:string" />
>  <xs:element minOccurs="0" name="szUserId" type="xs:string" />
>  <xs:element minOccurs="0" name="szProgramId" type="xs:string" />
>  <xs:element minOccurs="0" name="szWorkStationId" type="xs:string" />
>  <xs:element minOccurs="0" name="jdDateUpdated" type="xs:string" />
>  <xs:element minOccurs="0" name="mnTimeOfDay" type="xs:string" />
>  <xs:element minOccurs="0" name="cEdiSuccessfullyProcess" type="xs:string"
> />
>  </xs:sequence>
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
>  <xs:attribute fixed="AutocashItemXrefMBF" name="name" type="xs:string" />
>  <xs:attribute name="app" type="xs:string" use="optional" />
>  <xs:attribute name="returnNullData" type="xs:string" use="optional" />
>  <xs:attribute name="runOnError" type="xs:string" use="optional" />
>  <xs:attribute name="trans" type="xs:string" use="optional" />
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
>  <xs:attribute fixed="callmethod" name="type" type="xs:string" />
>  <xs:attribute name="user" type="xs:string" use="optional" />
>  <xs:attribute name="role" type="xs:string" use="optional" />
>  <xs:attribute name="session" type="xs:string" use="optional" />
>  <xs:attribute name="sessionidle" type="xs:string" use="optional" />
>  <xs:attribute name="environment" type="xs:string" use="optional" />
>  </xs:complexType>
>  </xs:element>
>  </xs:sequence>
>  </xs:complexType>
>  </xs:element>
>  </xs:schema>







[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Ellen Deak


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-09-06 12:17 AM

Yes, I typed in autocahsItemXrefMBFSoapOut. and used intellisense the rest o
f
the way down the line. That's one of the reasons why I'm really confused as
to why I don't get the value that ends up in the XML.
--
Ellen Deak


"Greg Forsythe" wrote:

> Ellen,
> The syntax for accessing a distinguished field is normally
> Message.DistinguishedField
> or in your case with multipart messages
> AutocashItemXrefMBFSoapOut.bodyPart.cEdiSuccessfullyProcess
>
> Normally intellisense will provide the distinguished field when you type t
he
> dot after the message type.
>
> Greg
>
>
> "Ellen Deak" <ellen@newsgroups.nospam> wrote in message
> news:4B4CFB5B-1876-45A1-8E4D-E24BC19EE3DE@microsoft.com... 
>
>
>





[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Greg Forsythe


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-09-06 12:18 PM

Ellen,
I think I found the problem.
The message instance does not match the schema.

The problem is namespace related.
The schema has the elementFormDefault property set to qualified, which means
all elements in the schema are in the targetnamespace.
In message, however only the root node is in the targetnamespace.
The <jdeResponse> node explicitly sets the namespace to null (xmlns="").

The quick fix is to open the schema, select the <Schema> node and set the
ElementFormDefault property to (Default) which is Unqualified.

A quick test is to save your message instance into a file and use the
Validate Instance test using that file.

Greg

"Ellen Deak" <ellen@newsgroups.nospam> wrote in message
news:520422B5-45A6-4B12-B410-55FC7608D723@microsoft.com...[vbcol=seagreen]
> Yes, I typed in autocahsItemXrefMBFSoapOut. and used intellisense the rest
> of
> the way down the line. That's one of the reasons why I'm really confused
> as
> to why I don't get the value that ends up in the XML.
> --
> Ellen Deak
>
>
> "Greg Forsythe" wrote:
> 







[ Post a follow-up to this message ]



    Re: Utilizing Distinguished Field  
Ellen Deak


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-13-06 12:17 AM

Thank you Greg. That solved the problem.
--
Ellen Deak


"Greg Forsythe" wrote:

> Ellen,
> I think I found the problem.
> The message instance does not match the schema.
>
> The problem is namespace related.
> The schema has the elementFormDefault property set to qualified, which mea
ns
> all elements in the schema are in the targetnamespace.
> In message, however only the root node is in the targetnamespace.
> The <jdeResponse> node explicitly sets the namespace to null (xmlns="").
>
> The quick fix is to open the schema, select the <Schema> node and set the
> ElementFormDefault property to (Default) which is Unqualified.
>
> A quick test is to save your message instance into a file and use the
> Validate Instance test using that file.
>
> Greg
>
> "Ellen Deak" <ellen@newsgroups.nospam> wrote in message
> news:520422B5-45A6-4B12-B410-55FC7608D723@microsoft.com... 
>
>
>





[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 11:38 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register