|
Home > Archive > BizTalk Server General > February 2005 > Space in a Field name
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 |
Space in a Field name
|
|
|
| Hi everyone,
Just wanted to know whether it is possible to have a space in the schema
element field name such as (User Name) in Biztalk 2004.
and also what are the characters that not allowed in a schema element field
name.
it's kinda urgent so please help,
Thank you .
| |
| Etienne Combaud 2005-02-03, 5:49 pm |
| Hi Kamal,
You could not include space in field or record names as they are translate
into XML attribute and element names respectively and XML doesn't allow
white space for them.
Etienne
"Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
news:%23wLvmFgCFHA.2600@TK2MSFTNGP09.phx.gbl...
> Hi everyone,
>
> Just wanted to know whether it is possible to have a space in the schema
> element field name such as (User Name) in Biztalk 2004.
>
> and also what are the characters that not allowed in a schema element
> field
> name.
>
> it's kinda urgent so please help,
>
> Thank you .
>
>
| |
|
| how about flat file and/or CSV file??
I'm translating an XML file without spaces to a flat file/ CSV with spaces
in the field names!!
"Etienne Combaud" <etienne.combaud@laposte.net> wrote in message
news:uY$UGUgCFHA.3908@TK2MSFTNGP12.phx.gbl...
> Hi Kamal,
>
> You could not include space in field or record names as they are translate
> into XML attribute and element names respectively and XML doesn't allow
> white space for them.
>
> Etienne
>
> "Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
> news:%23wLvmFgCFHA.2600@TK2MSFTNGP09.phx.gbl...
>
>
| |
| Etienne Combaud 2005-02-04, 7:50 am |
| Read documentation about the core system of BTS : it uses XSLT as the core
translator, so each format for inbound document are parsed to XML (except
XML of course) and the XML result of the XSLT translation (result of the
mapping) is serialized to the outbound format.
"Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
news:eVMMqogCFHA.3596@TK2MSFTNGP12.phx.gbl...
> how about flat file and/or CSV file??
>
> I'm translating an XML file without spaces to a flat file/ CSV with spaces
> in the field names!!
>
>
>
> "Etienne Combaud" <etienne.combaud@laposte.net> wrote in message
> news:uY$UGUgCFHA.3908@TK2MSFTNGP12.phx.gbl...
>
>
| |
|
| I'm afraid that's has not answered my question.
My question is very simple, a Field name (a node in a schema OR A Child
Field Element) called ( User Name), as you can see there is a space between
User and Name. When I try to insert the node name with the space, the schema
designer doesn't like it and would add _x0020_ as a value for the space. so
the element name will be User_x0020_Name. However, when sending the CSV
file, I want it to have the space (i.e. I want it to appear as User Name
with the space).
I hope i've made my question clearer.
"Etienne Combaud" <etienne.combaud@laposte.net> wrote in message
news:uFa0gkqCFHA.2676@TK2MSFTNGP12.phx.gbl...
> Read documentation about the core system of BTS : it uses XSLT as the core
> translator, so each format for inbound document are parsed to XML (except
> XML of course) and the XML result of the XSLT translation (result of the
> mapping) is serialized to the outbound format.
>
>
> "Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
> news:eVMMqogCFHA.3596@TK2MSFTNGP12.phx.gbl...
spaces[vbcol=seagreen]
>
>
| |
| Greg Forsythe 2005-02-08, 7:56 am |
| You cannot have a space in a node name within Xml.
This is not a restriction with Biztalk, it is inherent in all Xml.
This should not be a problem as the Xml node names cannot be output by the
FlatFileAssembler (which converts Xml to Csv) only the data (content in a
tag) can be output.
If you wish to output field names in the Csv, then you will need to define
attributes or elements within you Xml which will hold the field names. These
fields names will be data and so can have a space.
<UserName><fieldName>User
Name</fieldName><fieldContent>Fred</fieldContent></UserName>
or <UserName fieldName="User Name">Fred</UserName>
would become:
User Name,Fred
Greg
"Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
news:umNd97PDFHA.3732@TK2MSFTNGP14.phx.gbl...
> I'm afraid that's has not answered my question.
>
> My question is very simple, a Field name (a node in a schema OR A Child
> Field Element) called ( User Name), as you can see there is a space
between
> User and Name. When I try to insert the node name with the space, the
schema
> designer doesn't like it and would add _x0020_ as a value for the space.
so
> the element name will be User_x0020_Name. However, when sending the CSV
> file, I want it to have the space (i.e. I want it to appear as User Name
> with the space).
>
> I hope i've made my question clearer.
>
>
>
>
> "Etienne Combaud" <etienne.combaud@laposte.net> wrote in message
> news:uFa0gkqCFHA.2676@TK2MSFTNGP12.phx.gbl...
core[vbcol=seagreen]
(except[vbcol=seagreen]
> spaces
allow[vbcol=seagreen]
element[vbcol=seagreen]
>
>
| |
| Matt Milner 2005-02-08, 5:51 pm |
| The easiest way to accomplish this for a flat file is probably to define a
header schema that has one row which is your column headers. name the
elements whatever you like,then give them a fixed text value that is your
column name. In your send pipeline, choose this header schema along with
your document schema.
matt
"Greg Forsythe" <greg.forsythe@unisys.com> wrote in message
news:uquULecDFHA.1936@TK2MSFTNGP14.phx.gbl...
> You cannot have a space in a node name within Xml.
> This is not a restriction with Biztalk, it is inherent in all Xml.
>
> This should not be a problem as the Xml node names cannot be output by the
> FlatFileAssembler (which converts Xml to Csv) only the data (content in a
> tag) can be output.
> If you wish to output field names in the Csv, then you will need to define
> attributes or elements within you Xml which will hold the field names.
> These
> fields names will be data and so can have a space.
>
> <UserName><fieldName>User
> Name</fieldName><fieldContent>Fred</fieldContent></UserName>
> or <UserName fieldName="User Name">Fred</UserName>
> would become:
> User Name,Fred
>
>
> Greg
>
>
>
> "Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
> news:umNd97PDFHA.3732@TK2MSFTNGP14.phx.gbl...
> between
> schema
> so
> core
> (except
> allow
> element
>
>
| |
|
| Ok thanks guys. i think i got the idea. that's great.
Just one more questions, you know when u send a XML schema and would like to
receive a CSV (Flat file) File. I've created the schemas for both (XML &
CSV), the map between them, is that enough to create the ports and get the
file in csv? or do I have to use a pipeline and add the Flat file assembler
? Is there any other ways of doing it without having to create this
pipeline?
Appreciate your help and support. thanks to all of you.
Kamal
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:e97PrqeDFHA.3324@TK2MSFTNGP15.phx.gbl...
> The easiest way to accomplish this for a flat file is probably to define a
> header schema that has one row which is your column headers. name the
> elements whatever you like,then give them a fixed text value that is your
> column name. In your send pipeline, choose this header schema along with
> your document schema.
>
> matt
>
>
> "Greg Forsythe" <greg.forsythe@unisys.com> wrote in message
> news:uquULecDFHA.1936@TK2MSFTNGP14.phx.gbl...
the[vbcol=seagreen]
a[vbcol=seagreen]
define[vbcol=seagreen]
space.[vbcol=seagreen]
Name[vbcol=seagreen]
the[vbcol=seagreen]
>
>
| |
| Greg Forsythe 2005-02-09, 8:49 pm |
| You need to create a pipeline.
The outbound message is in Xml format until it is processed by the FlatFile
Assembler.
The Flat File assembler converts the Xml into a flat file using the
recordInfo and fieldInfo definitions in the schema.
Without the FlatFile Assembler the output will be XML.
Greg
"Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
news:#fWdf6qDFHA.3728@TK2MSFTNGP14.phx.gbl...
> Ok thanks guys. i think i got the idea. that's great.
>
> Just one more questions, you know when u send a XML schema and would like
to
> receive a CSV (Flat file) File. I've created the schemas for both (XML &
> CSV), the map between them, is that enough to create the ports and get the
> file in csv? or do I have to use a pipeline and add the Flat file
assembler
> ? Is there any other ways of doing it without having to create this
> pipeline?
>
> Appreciate your help and support. thanks to all of you.
>
> Kamal
>
>
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:e97PrqeDFHA.3324@TK2MSFTNGP15.phx.gbl...
a[vbcol=seagreen]
your[vbcol=seagreen]
> the
in[vbcol=seagreen]
> a
> define
Child[vbcol=seagreen]
> space.
CSV[vbcol=seagreen]
> Name
the[vbcol=seagreen]
of[vbcol=seagreen]
with[vbcol=seagreen]
doesn't[vbcol=seagreen]
> the
>
>
| |
|
| Thanks Greg,
I just thought there were any other way of doing! from the Orchestration for
instance but I guess there is not!!
Kamal
"Greg Forsythe" <greg.forsythe@unisys.com> wrote in message
news:OeN9lNxDFHA.2288@TK2MSFTNGP14.phx.gbl...
> You need to create a pipeline.
> The outbound message is in Xml format until it is processed by the
FlatFile
> Assembler.
> The Flat File assembler converts the Xml into a flat file using the
> recordInfo and fieldInfo definitions in the schema.
>
> Without the FlatFile Assembler the output will be XML.
>
> Greg
>
>
>
> "Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
> news:#fWdf6qDFHA.3728@TK2MSFTNGP14.phx.gbl...
like[vbcol=seagreen]
> to
the[vbcol=seagreen]
> assembler
message[vbcol=seagreen]
define[vbcol=seagreen]
> a
> your
with[vbcol=seagreen]
by[vbcol=seagreen]
> in
names.[vbcol=seagreen]
> Child
the[vbcol=seagreen]
> CSV
> the
> of
> with
message[vbcol=seagreen]
are[vbcol=seagreen]
> doesn't
in[vbcol=seagreen]
schema[vbcol=seagreen]
>
>
| |
| Greg Forsythe 2005-02-10, 7:50 am |
| If you were very keen, you could write a .Net component that would assemble
the Xml into a flat string, using the RawString formatter
You could call this from your orchestration and then use the PassThru
pipeline to send.
Your .Net component would replicate the function of the Xml Assembler,
without the pipeline wrapper.
There would be no advantage to this, you would have a lot of custom
code(support and maintenance issues) and installation hassles.
Using a Flat File Assembler in a pipeline achieves that same result without
the aggravation.
Greg
"Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
news:OO$IVt1DFHA.1524@TK2MSFTNGP09.phx.gbl...
> Thanks Greg,
>
> I just thought there were any other way of doing! from the Orchestration
for
> instance but I guess there is not!!
>
> Kamal
>
> "Greg Forsythe" <greg.forsythe@unisys.com> wrote in message
> news:OeN9lNxDFHA.2288@TK2MSFTNGP14.phx.gbl...
> FlatFile
> like
&[vbcol=seagreen]
> the
> message
> define
the[vbcol=seagreen]
> with
output[vbcol=seagreen]
> by
(content[vbcol=seagreen]
to[vbcol=seagreen]
> names.
space[vbcol=seagreen]
> the
the[vbcol=seagreen]
User[vbcol=seagreen]
as[vbcol=seagreen]
XML[vbcol=seagreen]
(result[vbcol=seagreen]
CSV[vbcol=seagreen]
> message
> are
> in
> schema
>
>
| |
|
| Thanks Greg, I'd rather use the pipline as i'm currently doing anyhow. :o)
"Greg Forsythe" <greg.forsythe@unisys.com> wrote in message
news:OZioTb2DFHA.548@TK2MSFTNGP14.phx.gbl...
> If you were very keen, you could write a .Net component that would
assemble
> the Xml into a flat string, using the RawString formatter
> You could call this from your orchestration and then use the PassThru
> pipeline to send.
> Your .Net component would replicate the function of the Xml Assembler,
> without the pipeline wrapper.
>
> There would be no advantage to this, you would have a lot of custom
> code(support and maintenance issues) and installation hassles.
> Using a Flat File Assembler in a pipeline achieves that same result
without
> the aggravation.
>
> Greg
>
> "Kamal" <kali@bca-group.comNOSPAMPLEASE> wrote in message
> news:OO$IVt1DFHA.1524@TK2MSFTNGP09.phx.gbl...
> for
(XML[vbcol=seagreen]
> &
get[vbcol=seagreen]
> the
is[vbcol=seagreen]
along[vbcol=seagreen]
Xml.[vbcol=seagreen]
> output
> (content
> to
A[vbcol=seagreen]
> space
space,[vbcol=seagreen]
the[vbcol=seagreen]
> the
> User
message[vbcol=seagreen]
XSLT[vbcol=seagreen]
> as
> XML
> (result
> CSV
they[vbcol=seagreen]
space[vbcol=seagreen]
>
>
|
|
|
|
|