- This topic has 3 replies, 1 voice, and was last updated 8 years, 3 months ago by
.
-
Posts
-
-
Here is the error message I receive:
Error 3 Node “Element.Part” – Specify a valid .NET type name for this root node. The current .NET type name of this root node is invalid (it is a reserved BizTalk Keyword or is an invalid C# identifier). …\loc.xsd
It appears using the ‘.’ in the element name is a no-no with biztalk. Unfortunately, I don’t have much choice because the schema is not mine. Even more interesting is that I have a working map that incorporates the schema using the ‘.’ elements, but when I incorporate into a working orchestration, I get an explosion of sorts.
Does anyone have any ideas on how to resolve the issue? I’m thinking perhaps a pipeline component that can replace the dots with underscores or something like that. I’m not sure what the best resolution would be. Any help is greatly appreciated.
-Bart
-
-
Thank you for the reply. Actually, I stumbled onto the answer earlier today.
If you click on the node in biztalk schema editor, in the properties window, there is a field called “RootNode TypeName”. In that field, I replaced the default with “Element_Part”. This is really nice because the incoming message will still conform to the original schema, but when biztalk builds the project to C#, it will treat the Element.Part as Element_Part.
It turns out it was a quick and easy fix for a potentially horrific problem.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.