Package com.appliedolap.essbase

Class EssBatchOutlineEdit.Action

java.lang.Object
com.appliedolap.essbase.EssBatchOutlineEdit.Action
Direct Known Subclasses:
EssBatchOutlineEdit.DimensionAction, EssBatchOutlineEdit.MemberAction
Enclosing class:
EssBatchOutlineEdit
public static class EssBatchOutlineEdit.Action extends Object
One action in the document.

Attributes are kept in insertion order and written as given. Names are the schema's, so a caller reading mbredit.xsd can follow what this produces line for line.

  • Method Details

    • attribute

      public EssBatchOutlineEdit.Action attribute(String name, Object value)
      Sets an attribute the builder does not otherwise expose.
      Parameters:
      name - the attribute name, as the schema spells it
      value - the value; null removes the attribute

    • byMemberId

      public EssBatchOutlineEdit.Action byMemberId()
      Says that the member names in this action are actually member ids.

      What EPM Cloud's exported documents use throughout: every thisMbr is a Planning GUID rather than a name. Rarely what you want against Essbase directly.

    • after

      public EssBatchOutlineEdit.Action after(String sibling)
      Puts the member right after the given sibling.

      Without it a new member goes first among its parent's children, not last - verified against 21c, where adding Jan, Feb and Mar under Q1 in that order, none of them placed, leaves Mar, Feb, Jan. To add members in order, pass each one the sibling added just before it. Dimensions are the exception: a dimAdd without a sibling did go after the others.

      Parameters:
      sibling - the member, under the same parent, that this one should follow