Many times we see that links within BizTalk map break when there is some change in the schema used in the map.
One of the reasons for maps to break the links is changing the target namespace of the source or destination schema. To avoid breaking of the links within map, we should set the Ignore Namespace for Links property of the map to “Yes”.
If the root node name changes in a schema, all the links within map break. You need to rebuild the links again or open the .btm file in notepad and replace the old root node name with new root node name.
Changing the version of the .net assembly housing custom functoids or helper functions used in the map breaks the links using those assemblies. In this case we should update the .btm file directly in notepad to update the version of the referenced assembly.
If the schema element/attribute name changes the associated links break. Adding new elements/attributes/records doesn’t break the existing links. Those changes are automatically reflected in the map when map is reloaded.
That's it.
One of the reasons for maps to break the links is changing the target namespace of the source or destination schema. To avoid breaking of the links within map, we should set the Ignore Namespace for Links property of the map to “Yes”.
If the root node name changes in a schema, all the links within map break. You need to rebuild the links again or open the .btm file in notepad and replace the old root node name with new root node name.
Changing the version of the .net assembly housing custom functoids or helper functions used in the map breaks the links using those assemblies. In this case we should update the .btm file directly in notepad to update the version of the referenced assembly.
If the schema element/attribute name changes the associated links break. Adding new elements/attributes/records doesn’t break the existing links. Those changes are automatically reflected in the map when map is reloaded.
That's it.
Posts
