Problem with Insert command in DRM and its remedy

One of the attribute that make DRM so unique and also made it evolve so drastically is its shared library for hierarchies, as always every system has its down side DRM is no exception for that.

DRM has a feature called flwo through that facilitates user to share the hierarchy from other hierarchy provided both of them should be in the same version.

you have created one hierarchy and updated all the properties for it, now when creating other hierarchy from scratch, DRM says the so and so node already existing in the version so that you can't add but you can insert.

You just need to insert the required hierarchy from the source that reduces your manual effort as well you can keep the consistency across the hierarchies in the version, let me restate same with an example.

Your current hierarchy needs "Resources" sub hierarchy, instead of building it from scratch you can insert it from the source.

  

Now if you try to remove “Gandhi” in your hierarchy then it will remove even in source hierarchy also since “parent child combination” is same, this causes major issues, When I dug DRM, I found one validation class “PropRemove”, it mandates to enter 3 parameters then Save the validation and assign the validation to the hierarchy.


        


Here I repeated the same property thrice, if the node I am trying to remove is mapped with the same value of the property (Custom.Expertise_Domain = Hyperion) then it pops up one Error box as below.

                     

You can mention any three properties and respective values which make the differentiation from one to other.


Happy learning :)