Ditaval Processing Order Different for Maps vs Transform
Posted: Mon Aug 19, 2019 6:16 pm
Hello,
I'm having an issue with the ditaval being processed at a different time depending on whether the ditaval is included in the map or if it's included as an argument in the transformation.
The content that has profiling assigned to it is shared content and some of the topics are used by another product (which includes links that are not part of my project). When the output is generated with the ditaval specified as an argument in the transformation, everything generates fine with no issues. When the output is generated with the ditaval referenced within the ditamap, I receive errors that Oxygen can't find content that should have been filtered out by the ditaval.
In the transformation, the argument is set to "early" which appears to be why it works (setting it to "late" produces the same errors that content cannot be found). Is there a way to get Oxygen to filter "early" when using the ditaval file in the map rather than specifying it in the transformation? Is there a recommended place in the map to reference the ditaval file?
The issues we're trying to work out is that our users have to create copies of our transformation templates for each output type and ditaval file. It would be a lot cleaner/simpler for our users to just reference the ditaval in their maps.
Thanks!
Mark
I'm having an issue with the ditaval being processed at a different time depending on whether the ditaval is included in the map or if it's included as an argument in the transformation.
The content that has profiling assigned to it is shared content and some of the topics are used by another product (which includes links that are not part of my project). When the output is generated with the ditaval specified as an argument in the transformation, everything generates fine with no issues. When the output is generated with the ditaval referenced within the ditamap, I receive errors that Oxygen can't find content that should have been filtered out by the ditaval.
In the transformation, the argument
Code: Select all
filter-stage
The issues we're trying to work out is that our users have to create copies of our transformation templates for each output type and ditaval file. It would be a lot cleaner/simpler for our users to just reference the ditaval in their maps.
Thanks!
Mark