How to Create an Integration Account Project in Visual Studio 2019
Jun 16, 2023
An Integration Account allows you to build Logic Apps with enterprise B2B capabilities by adding various necessary artifacts It serves as a central
Best Practices while working with Schemas Pattern restrictions
Feb 22, 2022
Yesterday, I spoke about how you can apply custom pattern restrictions to properly validate DateTime, Date, and Time formats inside elements or attributes You
BizTalk Schema Validation: DateTime Restrictions
Feb 21, 2022
Today I was involved in a BizTalk Schema importation that includes not-so-used restrictions on Date and Time element formats And that gave me the idea and
BizTalk Server Schema Editor getting blocked by Internet Explorer Enhanced Security Configuration
Oct 6, 2021
I have been working on a new BizTalk Server project for a new client for a few weeks Now that we are beginning the development phase, I was getting annoyed
BizTalk Server Tips and Tricks for developers: How to create a .NET class from a schema
Feb 17, 2021
When NET code makes more sense than adapters In some scenarios, using BizTalk adapters is not the best option For example, you may want to handle
Visual Studio BizTalk Schema Generator Wizard error: Error occurred while creating the BizTalk po...
May 18, 2020
After several days migrating BizTalk open‑source contributions—such as the BizTalk Mapper Extensions Utility Pack, Pipeline Components Extensions Utility
BizTalk JSON Schema Wizard: Error in JSON Instance File.XMLNodeConverter can only convert JSON th...
Aug 30, 2019
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
BizTalk WCF-ORACLEDB error: PL/SQL: ORA-00917: missing comma
Aug 20, 2018
In the last few months, I have been working with the ORACLE adapter, mainly doing direct insert operations on ORACLE tables, and as you might imagine, I found
Demystify Invalid type name error on BizTalk Schemas (Part II)
Jul 27, 2018
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




