3 Replies Latest reply on Mar 20, 2017 10:33 PM by Prashant Joshi

    I need help with ArcFM rec/post procedures

    Marc Ball

      Our enterprise geodatabase Default version is set to Protected.  As the GIS Administrator I must post all child versions to Default.

       

      I am using the ArcFM Session Manager toolbar to rec/post.  However after I hit Post and I check the Default version against the original child version I see the differences are still present.  I also see that a new grandchild version is created called SN_<number>_MMPOST (owned by SDE).

       

      Can someone please help me understand this process within ArcFM?  If I perform the rec/post outside of an ArcFM session it works as I would expect it to.

       

      Thanks,
      Marc

        • Re: I need help with ArcFM rec/post procedures
          Lane Howerton

          Hi Marc,

           

          I'm definitely not the expert you're probably looking for but have been using ArcFM for about 10 years now. The MM version always gets created as part of the posting process. If I remember correctly, the edited version is copied to it then it posts to default and then both the edit version and the MM version are deleted. Although sometimes they both hang around, hence the need for the Orphaned Cleanup tool in Catalog. Not sure about the problem you're having with the different posting processes....sorry.

           

          Lane

          • Re: I need help with ArcFM rec/post procedures
            Josh Pritt

            This may not answer all of your question but it is a great explanation of the Orphaned Version Cleanup Tool (mentioned by Lane above) and what it does with these _MMPOST versions among other things:

            Orphaned Versions Clean Up Tool

              • Re: I need help with ArcFM rec/post procedures
                Prashant Joshi

                Hi Marc,

                 

                I am totally in sync with Josh Pritt's explanation.

                Though I am also not expert but using on Session Manager since 12 yrs  hence will try to explain the same,

                Whenever post button hits on session manager toolbar  one temporary version gets created in background   as SN_<number>_MMPOST (owned by SDE).  Session manager actually posts this temporary version to parent ( default) version. Once this Temporary version gets posted.  original version session SN_<number>  marked as orphaned in SDE.Versions table as flag you can find it in  "Hidden" column  as  value  0 or 1  and session gets deleted from session manager.

                Further when  "Orphaned Version Cleanup Tool" is used in ArcCatalog  it reads this column  and versions those are posted or deleted from session manager gets cleaned  from system as no longer needed, later you can use compress  option to move the edits to base table from  delta ( A&D) tables.

                 

                In case of ESRI versions you need to manually delete versions after posting these versions does not get cleaned by FM Cleanup tool .

                 

                Hope this is useful.

                 

                Regards

                 

                Prashant