Forum Replies Created
-
Posts
-
You could wrap the functionality in another orchestration and use the Start Orchestration shape to call it. Start Orchestration calls other orchestreations asynchronously while the Call Orchestration shape calls it synchronously
First you will need to introduce the ApplicationDetails schema as a fact to the business rules composer. In the Business Rules Composer under Facts Explorer/XML Schemas/right click/Browse and browse to your .xsd file.
Next Create a policy with a rule. For this rule go to Facts Explorer/Vocabularies/Predicates and select the range vocabulary and drag it to the "IF" pane on the right.
Click on XML Schemas and drag ApplicationDetails.Age to the first value of the range routine. Put 50 to 100 for second two values. In the "THEN" pane set ApplicationDetails.ActionScore = 1
Repeat these steps for the rest of your range values.
You will need to use the Call Rules Shape in your orchestration. Set the Policy of the Call Rules shape to whatever you called the above policy and put the Schema instance as a parameter. Let me know if you encounter any problems.
Can you execute the procedure outside of BizTalk?
Is there a reason you are assigning the results to output parameters
Try
Select Loan.LoanID, Mortgage.LoanAmount From…
Not sure why you need to select into params. Just select the columns and then promote the schema attributes if you need to use those values.
SELECT Loan.LoanID,
Mortage.LoanAmt
FROM Loan
JOIN MortgageTerms on Mortage.MortageType = Loan.MortageType
WHERE Loan.LoanNumber = @Loan_Num FOR XML AUTO, XMLDATAOr if you need those names…
SELECT Loan.LoanID as [LnndCaseNum],
Mortage.LoanAmt AS [LnAmount ]
FROM Loan
JOIN MortgageTerms on Mortage.MortageType = Loan.MortageType
WHERE Loan.LoanNumber = @Loan_Num FOR XML AUTO, XMLDATANo need to put them to vairables unless you explain why you wanted that.
What is wrong with using Covast? There is more to it than just schemas; for example an EDI translator is supposed to be able to perform additional functions some of which I will list:
1. Document Validation in terms of compliance with X12 and Edifact EDI standards. Covast has a special language for expressing these rules that it validates at parse or serialize time. Your hacked standards will not implement compliance checking.
2. Presentation of detailed error messages for Compliance Violation. Shows you where your error or your partner's error(s) is.
3. Functional acknowledgement reconciliation
4. Enveloping options – there are a variety for EDI.
5. Archiving. Are you aware of the legal requirement to archive your EDI transaction for a period of 7 years?
etc.
As an EDI professional, it is not my recommendation to try to go into production with an application that you hacked into "working". In managing an EDI application, there is much more to consider than simply passing a document through an application.
It seems strange for Microsoft to enter agreement with a solution provider and then sneak in a KB article about a "hack" to entice users to avoid using their solution partner's product, does it not?
Do you all really believe that Microsoft is going to release schemas and that alone eliminates the need for Covast?
Paul,
You can use BizTalk Deployment Wizard to create Binding XML
export it and import the xml into u r customer server.
or
Create .MSI file and do the same…
Nar-
Paul,
You can use BizTalk Deployment Wizard to create Binding XML
export it and import the xml into u r customer server.
or
Create .MSI file and do the same…
Nar-
Seems you could have skipped this if you had defined your parsing schema as having 'NoteToRecord' element subordinate to the 'Record' element.
i.e Record contains 0 or more NoteToRecord
This is assuming you are parsing. otherwise the generator fo the source XML could have stacked NoteToRecord subordinately.
parsing each transaction is how it is designed to work.
Can you describe the requirement to join them all into one XML file? Do you need to generate a summary across all invoices from a batch?
have a look this blog:
http://blogs.conchango.com/matthall/archive/2005/07/28/1894.aspx
Hope you got some information.
Nar-
I figured it out, it's caused by non-exists reference path in project.
Right click the project > Properties, in the Pop-uped the window, go to the "Referenced Paths", check if there's any path not exists anymore, this will happen when you move the solution to another machine.
Delete those path and deploy it, everything's working fine. 🙂
Hi, I would really like to know how you did it? What I'm trying to do this is following.
Problem: Needs to access some value from .NET class while processing the rules.
Approach: I created a class library with one property called public string getData {get{return "Hello World";";}}
I registered the resulting dll in the GAC tool.
I then created a new Vocabulary in the BizTalk Rules engine and added a definition of to retrieve data from .NET Class.
I then selected my DLL using the BROWSE button.
When I'm using this vocabulary in my rules, the string "Hello World" is not being returned? Also I think the whole rule cease to executed if I use my new vocabulary.
I'm not sure what is happening. Any help will be appreciated.
Iftikhar.
I had a couple of problems….
The error 'method does not exist' was caused by the fact I hadn't ….
added generated item
added adapter metadata
oracle database … created for the the sendport that I had previously definedThe namespace wasn't quite right, should have been …
h ttp://schemas.microsoft.com/[MyOracleDbAdapter://MYDATABASE/MYBIZTALKSCHEMA/Tables/SAMPLE_XCHANGE]
Last, I did validate the schema, generate instance and then validate instance.
