Xml failure while validating management pack
Each element in management pack (class, relationship, enumeration and so on) has a two independent key property when used in SDK: Name and ID.
And it can be little confusing here, because there is no Name attribute in management pack schema.
The answer is simple: the ID attribute in management pack is equal to Name property in SDK.
For instance, here is definition of the Active status enumeration for Incident class in management pack: and we must use ID attribute value as Name in SDK..
If you often using the XML criteria in SCSM (with SDK or in view with Advanced View Editor) then you can faced with two different notation used as value for properties of enumeration type (like Status, Category, Area and so on): $MPElement[Name=’’]$ and Guid format (xxxxxxxx-xxxx-xxx-xxxx-xxxxxxxxxxxx, or uniqueidentifier in T-SQL).
In this article I will describe the deference and will explain why XML validation can fail when $MPElement$ notation used.
This tutorial explains the procedure of validating an XML document with an XML schema.
Here is an example: Editing MPs by hand is not for the faint of heart, but it is a great way to debug problems, make bulk edits, reverse engineer things, do things which cannot be done via the UI, or revert changes that cannot be undone via the UI.This token can be used in queries, as parameter for workflow and in other places.This token will replaced by ID of management pack object.The SDK’s ID property aren’t stored in management pack but in database only and it’s calculated at moment when management pack imported into SCSM.The ID calculated using the SHA algorithm based on management pack name, management pack public key (only if MP is sealed) and name of the object.
Search for xml failure while validating management pack:
First of all, let’s talk about what is $MPElement$ notation.