May 23
BizTalk Server deployment error: a porttype operation can only contain messagetypes or class types
Welcome back to another blog post on this saga of Errors and Warnings, Causes, and Solutions Sometimes, I think that I'm a magnet that attracts errors, or
Apr 23
BizTalk Server WCF-SQL: Invalid object name while using temporary tables
It is pretty common to use temporary tables to perform some internal logic inside your SQL queries or scripts I have seen several
Jun 16
How to Create an Integration Account Project in Visual Studio 2019
An Integration Account allows you to build Logic Apps with enterprise B2B capabilities by adding various necessary artifacts It serves as a central
Feb 22
Best Practices while working with Schemas Pattern restrictions
Yesterday I spoke about how you can apply custom pattern restrictions to properly validate DateTime, Date, and Time formats inside elements or attributes You
Feb 21
BizTalk Schema Validation: DateTime Restrictions
Today I was involved in a BizTalk Schema importation that includes not-so-used restrictions on Date and Time elements formats And that gave me the idea and
Feb 17
BizTalk Server tips and tricks for developers: How to create a .NET class from a schema
Sometimes we want to bypass the adapters and perform the communication thru NET code Sometimes we want to access multiple values, or recursive values, of a
Aug 30
BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON th...
This week while trying to use the BizTalk Server 2016 JSON Schema Wizard to generate an XML schema from a specific JSON file to be sent to a Logic App I got
Aug 20
BizTalk WCF-ORACLEDB error: PL/SQL: ORA-00917: missing comma
In the last months, I have been working with ORACLE adapter, mainly doing direct insert operations on ORACLE tables and as you might imagine, I found some
Jul 27
Demystify Invalid type name error on BizTalk Schemas (Part II)
In the last post, we try to demystify the reason and cause of the error: Invalid type name The root node type has to be a valid C# identifier when you are
Jul 26
Demystify Invalid type name error on BizTalk Schemas (Part I)
A few days ago, while trying to compile a BizTalk Server solution I got the following error: Invalid type name The root node type has to be a valid C#
