- Fixed an issue where the username and password passed via the command line were improperly logged
- Fixed an issue reading MaxL XML data sources when the alias or UDA contained xml encoded characters such as the ampersand (&) character.
- Updated labels on the Input Source tab of the user interface to clarify their purpose.
Due to the architecture of the Oracle Essbase APIs, it is generally much faster to use the MaxL Outline XML extracts when processing an Essbase Outline extract. The Next Generation Outline Extractor still uses the Essbase Java API during this extract, but it is able to minimize the number of calls. The second option shown above, Extract and Process MaxL Outline XML, will automatically extract the Outline XML from the cube during the processing. The third option shown, Use Previously Extracted MaxL Outline XML, uses (obviously) an Outline XML file that has already been extracted.
Thank you to everyone who reported issues or made suggestions as you help make this utility better!
Posts
