community-content

Forum Replies Created

Viewing 15 posts - 3,181 through 3,195 (of 9,648 total)
  • Author
    Posts
  • in reply to: My own EDI schema #21763

    This post really helped to get a headstart into creating my own EDIFACT schema. the stylusstudio website is really a great place to refer to for EDFACT schema.

    in reply to: Fetch lookup Data from MS CRM 4.0 #21761

    Hi kuldip01.

    Try that:
    In yours BizTalk Administration Console\SomeAplication\SendPort you must have port called like CRMSendPort that send your requests to CRM.
    Make sure that SendPipeLine and RecievePipeLine = XMLTransmit and XMLRecieve.

    Andrew.
    [email protected]

    in reply to: Migratation BTS 2002 to BTS 2006 #21759

    The mapper creates xsl with embedded VBscript as the functoids.  YOu can take the xsl and process it with xslttransform.  The AIC is another problem though, if there is any business rules in the code.

     

    typically its a rewrite.

    in reply to: .NET assembly in business rule engine. Please help urgently ! #21754

    I got it, just need to add a registry entry

    at HKLM\Softwares\Microsoft\Business Rules\3.0\

    Add “StaticSupport” a DWORD value = 1.

    [Y]

    in reply to: How to Debug a Custom C# Component Called by BizTalk #21752

    Normal
    0

    false
    false
    false

    EN-US
    X-NONE
    X-NONE

    MicrosoftInternetExplorer4

    <!–
    /* Font Definitions */
    @font-face
    {font-family:”Cambria Math”;
    panose-1:2 4 5 3 5 4 6 3 2 4;
    mso-font-charset:1;
    mso-generic-font-family:roman;
    mso-font-format:other;
    mso-font-pitch:variable;
    mso-font-signature:0 0 0 0 0 0;}
    @font-face
    {font-family:Calibri;
    panose-1:2 15 5 2 2 2 4 3 2 4;
    mso-font-charset:0;
    mso-generic-font-family:swiss;
    mso-font-pitch:variable;
    mso-font-signature:-1610611985 1073750139 0 0 159 0;}
    /* Style Definitions */
    p.MsoNormal, li.MsoNormal, div.MsoNormal
    {mso-style-unhide:no;
    mso-style-qformat:yes;
    mso-style-parent:””;
    margin-top:0in;
    margin-right:0in;
    margin-bottom:10.0pt;
    margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    .MsoChpDefault
    {mso-style-type:export-only;
    mso-default-props:yes;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:Calibri;
    mso-fareast-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:”Times New Roman”;
    mso-bidi-theme-font:minor-bidi;}
    .MsoPapDefault
    {mso-style-type:export-only;
    margin-bottom:10.0pt;
    line-height:115%;}
    @page Section1
    {size:8.5in 11.0in;
    margin:1.0in 1.0in 1.0in 1.0in;
    mso-header-margin:.5in;
    mso-footer-margin:.5in;
    mso-paper-source:0;}
    div.Section1
    {page:Section1;}
    –>

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:”Table Normal”;
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:””;
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin-top:0in;
    mso-para-margin-right:0in;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0in;
    line-height:115%;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:”Calibri”,”sans-serif”;
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:”Times New Roman”;
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}

    Great work

    in reply to: Detecting duplicate nodes in BizTalk #21751

    The case is like this: A flat file of item master will be extracted daily with item code, description, and price respectively.  The flat file may consists of duplicate item records which the first one is the creation of item master and the second is the updated one.  I need to convert these records into XML file and only the last updated one is needed.  So I need to filter the duplicate ones and get the latest ones into my XML file.

    I have created a flat file schema and an XML file schema respectively on these fields.  I have also created a map to link them up.  An orchestration is created to receive the flat file and transform through the map and send to XML file.

    Any samples and hints?

    in reply to: Detecting duplicate nodes in BizTalk #21750

    You can sometimes achieve filtering using logical comparison functoids but other times custom Xslt is required.

    What is the record structure. What are you filtering on: fixed codes that are known at design time or Id values that are dynamic. What are the rules around filtering, map the first record and delete the rest, delete all except the last. Select one of the records based on some contained value? Find the record with the biggest value?

    in reply to: Detecting duplicate nodes in BizTalk #21749

    Thanks.  But what should I do with the map?

    I already created a map to link up between the flat file schema and the XML schema.  Should I use functoid to filter out unwanted records?  Could you please give an example?

    in reply to: invalid xml document error. #21748

    Does the element represented by the distinguished field “Title” exist in Msg1

    When you construct Msg1 you must ensure that any element or attribute that you wish to assign a value to must exist. The Xpath function and property assignment functions will not create an element in a message, only populate an existing element.  

    in reply to: Question to parse flat file #21747

    <? xml version=“1.0“ encoding=“utf-16“?>
    <
    xs:schema xmlns:b=“http://schemas.microsoft.com/BizTalk/2003“ xmlns=“http://FlatFileParse1.FlatFileSchema1“ targetNamespace=“http://FlatFileParse1.FlatFileSchema1“ xmlns:xs=“http://www.w3.org/2001/XMLSchema“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:schemaInfo standard=“Flat File“ root_reference=“Root“ default_pad_char=“ “ pad_char_type=“char“ count_positions_by_byte=“false“ parser_optimization=“speed“ lookahead_depth=“3“ suppress_empty_nodes=“false“ generate_empty_nodes=“true“ allow_early_termination=“false“ early_terminate_optional_fields=“false“ allow_message_breakup_of_infix_root=“false“ compile_parse_tables=“false“ />
    <
    schemaEditorExtension:schemaInfo namespaceAlias=“b“ extensionClass=“Microsoft.BizTalk.FlatFileExtension.FlatFileExtension“ standardName=“Flat File“ xmlns:schemaEditorExtension=“http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element name=“Root“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ sequence_number=“1“ child_order=“postfix“ child_delimiter_type=“hex“ child_delimiter=“0x0D 0x0A“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element maxOccurs=“unbounded“ name=“Batch“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo sequence_number=“1“ structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ child_order=“infix“ child_delimiter_type=“hex“ child_delimiter=“0x0D 0x0A“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <xs:element name=“Header“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo sequence_number=“1“ structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ tag_name=“10“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element name=“Field“ type=“xs:string“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:fieldInfo sequence_number=“1“ justification=“left“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    <
    xs:element name=“Detail“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ sequence_number=“2“ child_order=“infix“ child_delimiter_type=“hex“ child_delimiter=“0x0D 0x0A“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element minOccurs=“0“ name=“Type20“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo sequence_number=“1“ structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ tag_name=“20“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element name=“Field“ type=“xs:string“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:fieldInfo sequence_number=“1“ justification=“left“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    <
    xs:element minOccurs=“0“ maxOccurs=“unbounded“ name=“Type30“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ tag_name=“30“ sequence_number=“2“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element name=“Field“ type=“xs:string“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:fieldInfo sequence_number=“1“ justification=“left“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    <
    xs:element name=“Trailer“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:recordInfo sequence_number=“3“ structure=“delimited“ preserve_delimiter_for_empty_data=“true“ suppress_trailing_delimiters=“false“ tag_name=“90“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:complexType>
    <
    xs:sequence>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:groupInfo sequence_number=“0“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    <
    xs:element name=“Field“ type=“xs:string“>
    <
    xs:annotation>
    <
    xs:appinfo>
    <
    b:fieldInfo sequence_number=“1“ justification=“left“ />
    </
    xs:appinfo>
    </
    xs:annotation>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    </
    xs:sequence>
    </
    xs:complexType>
    </
    xs:element>
    </xs:schema> 

     

    in reply to: Detecting duplicate nodes in BizTalk #21745

    The flat file disassembler will not filter records. You will need to construct a flat file schema and parse the entire  flat file and then use a map (either in the receive pipeline or in an orchestration)  to filter out unwanted records.

    We will need a description of the incoming file (e.g. example of the parsed Xml file) and specifics about which codes are duplicates and need to be filtered out.

    in reply to: Custom Pipeline Component: xsl transform #21744

    Thank you for the replies.  I’ll be receiving the message via a biztalk webservice generated by the Biztalk Web Publishing wizard.  Or that’s at least what I had planned.  I was planning to publish an external schema which is essentially 2 nodes.  One for messageType and the other for the actual message parsed as a string.

    Another thing to note is that we will end up having flat files sent to us.  Which means that we would need to publish the schema so the translation can occur.  Which also means that every time there is a new exchange, we would need to redeploy our biztalk solution.

    Thanks for the suggestion Suman.  I think I’ll look deeper into that.

    in reply to: orchestration frustration… #21743

    Hi,

    I am not clear, if wo map orchestartion fullfill your equirement …why you need map…in the orchestartion are you calling SP thru SQLAdapter?  in the orchestartion working find means you did not use the transform shap which is calling ur map – correct?

    Can u tell some thing about your orchestartion process…what you need?

     

    in reply to: using orchestration as webservice in .net code #21742

    you can publish your orchestartion as webservice using viward…but remenber some ponts

    1) virtual directives must be highly isolated. if you do this OS will automatically create one component service.

    2) receive port use as RAR because if you publish orchestration as web service ..receive and send will be mane port

    3) Disable the retry method inside orchestration send port ow application performance will goes down

    4) use Delivery notification = trasmited

    Regards – suman kalyan betal

     

    in reply to: using orchestration as webservice in .net code #21741

    Hi,

       to do the xml serialization you need to create two applications

    1) one web application without user Interface means, if you run it will show the target xml file.  (with have URL / Port / own channel )

    2) create one window base application to host, we can create window service or simple console application which run 24/7 mode…it will always check the any request has come on the particular URL / Port / channel …then this host application take the input xml file and do the pocess and return the new  xml file which will match with your type message

     

     

     

Viewing 15 posts - 3,181 through 3,195 (of 9,648 total)