SQL Adapter - attributes treated like stored procedures - why?
Hello,
I've created a simple BizTalk application that uses a SQL Adapter to call a stored procedure. I used the "Add Generated Items" option to create the schema for the send port. The send pipeline uses XmlTransmit. The application also contains a simple map for the 5-element test document that I created. The input document contains 5 elements and the stored procedure has 5 parameters so that the text value for each element can be passed to the sproc.
When I first ran BizTalk I got a message that my stored procedure couldn't be found, but the name of the "missing" sproc was the first element in my receive document and not the real stored procedure name. I created a stored procedure for each of my 5 element names and now the orchestration runs to completion. I have verified that it calls each of the 5 stored procedures.
In short, instead of calling the correct stored procedure and passing it 5 parameters, my orchestration is calling 5 stored procedures.
What could possibly cause BizTalk to treat the element names as stored procedures?
I've included the send port (SQL Adapter) schema below.
Thanks for all assistance.
chema xmlns:b="http://schemas.microsoft.com/BizTalk/2003" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://SprocTest" version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">qlScriptvalue="exec [BizTalkToCustomerInsert] @Address=" ", @City=" ", @CustomerName=" ", @PostalCode=" ", @Region=" "" xmlns:msbtssql="http://schemas.microsoft.com/BizTalk/2003" />tring" />tring" />tring" />tring" />tring" />equence>chema>
BlackCatBone wrote: