You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

How to suppress "empty" hierarchy branches in a subscription

Accepted answer


Looking for input on how others have handled EDMCS/FCGL integrations, where upper levels of dimension hierarchy are set by an external organization, with internal posting-level members added later. Specifically, how to manage integration issues with "Summary" and "Allow Posting" properties, for those members which should always be Summary-only but initially are childless, yet may have children added later.

Content (required):

Our client campus has a series of dimension hierarchies that are defined at a state level, to which their local chart of accounts must conform; this means that the state defines the Summary nodes, while the campus defines the Allow Posting nodes. All Posting nodes occur at the same CoreStats.Level value (i.e. the chart is not 'ragged'). The chart is built and maintained in a Universal application, to which an FCGL application is subscribed.

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!