5 Replies Latest reply: Aug 13, 2014 11:21 PM by Denzz RSS

    Imports and PrimaryNodeName

    user507190

      Hello,

      I have a hierarchy with tons of shared members.  I have enable shared members = true.  When I import the hierarchy the prefix etc. is attached to the original member name as expected for all shared members.  However, the Core.PrimaryNodeName also includes the 'Shared:0000' prefix.  I expected that the PrimaryNodeName would represent the original node name without the prefix etc.  If I manually add a shared member, the primary node name property reflects the original node name without the prefix.  If I create a new shared node using an action script the primary node name also remains intact.  My question is if this is the expected behavior during the import?  If there something I am missing during the import process?

       

      Thanks!

        • 1. Re: Imports and PrimaryNodeName
          Denzz

          Hi,

           

          Could you please provide a sample writeup/snapshot of your import file, the various sections in it.Also, what version of DRM are you on?

           

          Thanks

          Denzz

          • 2. Re: Imports and PrimaryNodeName
            user507190

            Hello Denzz,

            My import has three sections - Hier / Relation / Node.

            The Hier section includes the following properties:  Hierarchy Name / Top Node / Primary Hierarchy / Enable Shared Members / Standard Hierarchy Sort

            The Relation section includes the following properties:  Parent Node / Name / IsPrimary

            The Node section includes the HFM.properties

             

            DRM Version = 11.1.2.2.310.

             

            Another question:  I 'thought' the shared members would assume the global properties of the primary node.  The HFM properties are 'Global' and yet when I import shared members they are not picking up the property values of the primary member.  Thoughts?

             

            Thanks in advance for your help!

            • 3. Re: Imports and PrimaryNodeName
              Denzz

              I don't see a reason. why the import should behave like this, will need to have the import file handy to check out what's going wrong... has to be something with the file.

               

              The IsPrimary property in the relationship section which property is that? Core or Custom?

               

              Also, how is the "Filter" tab setup in your import profile?

               

              Thanks

              Denzz

              • 4. Re: Imports and PrimaryNodeName
                user507190

                Hi Denzz,

                The IsPrimary property is included in the Relation section of the import and uses the EPMA.IsPrimary property.  The filters tab have all selected EXCEPT Inheriting properties (Skip id equal to Inherited value) and Derived Properties (Skip if equal to calculated value).  Sample Import looks like this:

                 

                [hier]

                A_ENT_None|ENT_None|TRUE|TRUE|Core.SortOrder

                B_ENT_AAZ|ENT_AAZ|TRUE|TRUE|Core.SortOrder

                C_ENT_AAA|ENT_AAA|FALSE|TRUE|Core.SortOrder

                D_ENT_CLS|ENT_CLS|FALSE|TRUE|Core.SortOrder

                 

                [relation]

                ENT_None|[None]|Y

                ENT_AAZ|AAZ|Y

                AAZ|106|Y

                106|116|Y

                116|115|Y

                115|110|Y

                115|CAD|Y

                 

                [node]

                [None]|Y|USD|N|N|||N|||||[None]

                AAZ|Y|USD|N|N|||N|E_All||||blablabal Consolidated

                106|Y|USD|N|N|||N|E_All||||xxxxxxxxxxxxxxxxxxx, LLC

                116|Y|USD|N|N|||N|E_All||||zzzzzzzzzzzzzzzzzz, 22222 GP

                115|Y|USD|N|N|||N|E_All||||vvvvvvvvvvvvvvvvvvvvvvvvvvv, 33333 GP

                 

                Node properties = Node, Currency, allowAdj, allowAdjfromchild,holdingcompany,securityaspartner,isicp,securityclass, UD1, UD2, UD3, desc

                 

                Your assistance is greatly appreciated!

                • 5. Re: Imports and PrimaryNodeName
                  Denzz

                  Hi,

                   

                  This snapshot of the import file does not show a node which would be created as Shared Node, what i mean to say is if you look at the Relation section i don't see a node that could potentially become a shared node on import.

                   

                  Also if you take a look at the relation section

                   

                  ENT_None|[None]|Y

                  ENT_AAZ|AAZ|Y

                  AAZ|106|Y

                  106|116|Y

                  116|115|Y

                  115|110|Y

                  115|CAD|Y

                   

                  what is the parent for ENT_AAZ?

                   

                  Thanks

                  Denzz