- 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
5 comments:
Thanks Tim,
With this fix, I can change my process to use the XML format. It will take my small cube export from 72 seconds to 12 seconds. It is amazing how much faster the XML extract is.
Hello Tim,
I've been trying to use the new version of the utility but I'm facing an issue with UDA extraction. To be more precise, using output.handlers=DOCUMENTATION_TEXT_FORMAT, I'm extracting a dimension with 4 different values for the UDA. However, in the output generated, the 4 UDA columns contain only one value (which repeats itself on the other 3 UDA columns).
...;UDA: 0;UDA: 1;UDA: 2;UDA: 3
...; EUR; EUR; EUR; EUR
Do you know how if there's a workaround for this issue?
Thank you for your help.
Regards,
Andy
Hello Tim,
I've been trying to use the new version of the utility but I'm facing an issue with UDA extraction. To be more precise, using output.handlers=DOCUMENTATION_TEXT_FORMAT, I'm extracting a dimension with 4 different values for the UDA. However, in the output generated, the 4 UDA columns contain only one value (which repeats itself on the other 3 UDA columns).
...;UDA: 0;UDA: 1;UDA: 2;UDA: 3
...; EUR; EUR; EUR; EUR
Do you know how if there's a workaround for this issue?
Thank you for your help.
Regards,
Andy
Please report issues to support@appliedolap.com. Thanks!
Tim
Andy,
We have replicated the issue and will be making a change to resolve the issue.
Tim
Post a Comment