The interrogation rule itself looks ok. However, if you also have the base ISO 19115 profile active AND if the interrogation rule for ISO 19115 is before your custom profile, the metadata may still be interpreted as ISO 19115. That is because the rule for ISO 19115 is:
{
key: "iso-19115",
requiredPath: "esri/dijit/metadata/types/iso/base/DataDocumentType",
interrogationRules: [{
path: "/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification",
must: true
}]
},
And means your ISO-based metadata will still be recognized by this rule. You have two options:
That did the trick, moving the custom profile to the top of the list. Thank you kind sir!
Hi Marten,
I'm also going through the same situation. while saving the myprofile metadata I'm getting the following error. any help will be appreciated. ( I have added the console error as well )