When an entity is specified to be loaded, a load mask is required to tell Odyssey which items within that entity should be
loaded. For example, within the case entity, there are many different areas of data which may or may not be loaded, such as
parties, charges, events, warrants, and hearings.
To specify what items to load, a bitmapped load mask is used. Using the case entity as an example, the party item is specified
by a "1," the relations items is specified by a "2," charges with a "4," events with an "8," and so on.
To specify loading the case entity with the parties, charges, and events items, you add 1 + 4 + 8 = 13, and use a load mask
of 13.
The Bitmask Calculator dialog box automatically calculates the load masks for pre and post evaluation loads.
Click Copy to copy the load mask to the clipboard.
Edit that figure into the XML Fragment in the Pre-evaluation Loads field or Post-evaluation Loads field, in the LoadMask attribute within the entity.
The following is an example of a case entity XML fragment:
<Case LoadMask=”2147483647”> </Case>
The following is an example of the case entity as a parent with party and warrant entities as children:
<Case LoadMask=”2147483647” >
<Party LoadMask=”2147483647”/>
<Warrant LoadMask=”2147483647”/>
</Case>