BizTalk Server General - Why I cant Promote this.?

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > July 2005 > Why I cant Promote this.?





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Why I cant Promote this.?
Luis Esteban Valencia

2005-07-14, 5:51 pm

Hello. I am trying to promote the quantity property but I cant. I need to
use that quantity in an orchestration to use a decide shape.

Thanks

<?xml version="1.0" encoding="utf-16" ?>
- <xs:schema xmlns:tns="http://BTSDG_SQL"
xmlns:ns0="http://BiztalkSQL.PropertySchemaBusinessCard"
xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://BTSDG_SQL"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
- <xs:annotation>
- <xs:appinfo>
- <imports xmlns="http://schemas.microsoft.com/BizTalk/2003">
<namespace prefix="ns0" uri="http://BiztalkSQL.PropertySchemaBusinessCard"
location=".\propertyschemabusinesscard.xsd" />
</imports>
</xs:appinfo>
</xs:annotation>
- <xs:element name="BusCard_Request">
- <xs:complexType>
- <xs:sequence>
- <xs:element xmlns:updategram="urn:schemas-microsoft-com:xml-updategram"
updategram:Prefix="updg" minOccurs="1" maxOccurs="unbounded" name="sync">
- <xs:complexType>
- <xs:sequence>
- <xs:element updategram:Prefix="updg" minOccurs="0" maxOccurs="unbounded"
name="after">
- <xs:complexType>
- <xs:sequence>
- <xs:element minOccurs="0" maxOccurs="unbounded" name="BusinessCards">
- <xs:complexType>
<xs:attribute name="NameOnCard" type="xs:string" />
<xs:attribute name="TitleOnCard" type="xs:string" />
<xs:attribute name="Quantity" type="xs:int" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
- <xs:element name="BusCard_Response">
- <xs:complexType>
- <xs:sequence>
<xs:element name="Success" type="xs:anyType" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>


Scott Colestock

2005-07-14, 5:51 pm

At a quick glance, it looks like your quantity property (or containing
element) can appear more than once - BizTalk won't allow you to
promote/distinguish this because the reference is ambiguous.

Scott Colestock
www.traceofthought.net



"Luis Esteban Valencia" <levalencia@avansoft.com> wrote in message
news:ujN$oxIiFHA.3692@TK2MSFTNGP09.phx.gbl...
> Hello. I am trying to promote the quantity property but I cant. I need to
> use that quantity in an orchestration to use a decide shape.
>
> Thanks
>
> <?xml version="1.0" encoding="utf-16" ?>
> - <xs:schema xmlns:tns="http://BTSDG_SQL"
> xmlns:ns0="http://BiztalkSQL.PropertySchemaBusinessCard"
> xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
> attributeFormDefault="unqualified" elementFormDefault="qualified"
> targetNamespace="http://BTSDG_SQL"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> - <xs:annotation>
> - <xs:appinfo>
> - <imports xmlns="http://schemas.microsoft.com/BizTalk/2003">
> <namespace prefix="ns0"
> uri="http://BiztalkSQL.PropertySchemaBusinessCard"
> location=".\propertyschemabusinesscard.xsd" />
> </imports>
> </xs:appinfo>
> </xs:annotation>
> - <xs:element name="BusCard_Request">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element xmlns:updategram="urn:schemas-microsoft-com:xml-updategram"
> updategram:Prefix="updg" minOccurs="1" maxOccurs="unbounded" name="sync">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element updategram:Prefix="updg" minOccurs="0" maxOccurs="unbounded"
> name="after">
> - <xs:complexType>
> - <xs:sequence>
> - <xs:element minOccurs="0" maxOccurs="unbounded" name="BusinessCards">
> - <xs:complexType>
> <xs:attribute name="NameOnCard" type="xs:string" />
> <xs:attribute name="TitleOnCard" type="xs:string" />
> <xs:attribute name="Quantity" type="xs:int" />
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> - <xs:element name="BusCard_Response">
> - <xs:complexType>
> - <xs:sequence>
> <xs:element name="Success" type="xs:anyType" />
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:schema>
>
>



Luis Esteban Valencia

2005-07-14, 5:51 pm

Can u please tell me what I need to Dol? Should I change the XML schema and
not no allow more than one record per file?


"Scott Colestock" <scolestock@community.nospam> escribió en el mensaje
news:edHSv3IiFHA.2904@tk2msftngp13.phx.gbl...
> At a quick glance, it looks like your quantity property (or containing
> element) can appear more than once - BizTalk won't allow you to
> promote/distinguish this because the reference is ambiguous.
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "Luis Esteban Valencia" <levalencia@avansoft.com> wrote in message
> news:ujN$oxIiFHA.3692@TK2MSFTNGP09.phx.gbl...
to[vbcol=seagreen]
xmlns:updategram="urn:schemas-microsoft-com:xml-updategram"[vbcol=seagreen]
name="sync">[vbcol=seagreen]
maxOccurs="unbounded"[vbcol=seagreen]
>
>



Scott Colestock

2005-07-14, 5:51 pm

If you indeed won't have more than one record per file, then yes, do that.

Otherwise, assign the quantity to an integer variable in your orchestration,
using the xpath function in an expression shape that grabs the node you
want. Then you can have your decision shape reference that variable.

Scott Colestock
www.traceofthought.net


"Luis Esteban Valencia" <levalencia@avansoft.com> wrote in message
news:ueBHTNJiFHA.1044@tk2msftngp13.phx.gbl...
> Can u please tell me what I need to Dol? Should I change the XML schema
> and
> not no allow more than one record per file?
>
>
> "Scott Colestock" <scolestock@community.nospam> escribió en el mensaje
> news:edHSv3IiFHA.2904@tk2msftngp13.phx.gbl...
> to
> xmlns:updategram="urn:schemas-microsoft-com:xml-updategram"
> name="sync">
> maxOccurs="unbounded"
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com