DataExportDynamicCalc ON | OFF
ON—(Default) Dynamically calculated values are included in the export.
OFF—No dynamically calculated values are included in the report.
Specifies whether a text data export excludes dynamically calculated data.
Text data exports only. If DataExportDynamicCalc ON is encountered with a binary export (DATAEXPORT BINFILE …) it is ignored. No dynamically calculated data is exported.The DataExportDynamicCalc option does not apply to attribute values.If DataExportLevel INPUT is also specified and the FIX statement range includes sparse Dynamic Calc members, the FIX statement is ignored.
DataExportNonExistingBlocks ON | OFF
ON—Data from all possible data blocks, including all combinations in sparse dimensions, are exported.
OFF—(Default) Only data from existing data blocks is exported.
Specifies whether to export data from all possible data blocks. For large outlines with a large number of members in sparse dimensions, the number of potential data blocks can be very high. Exporting Dynamic Calc members from all possible blocks can significantly impact performance.
Furthur testing reveals that with DataExportNonExistingBlocks and DynamicCalc Sparse parent member it won’t export missing blocks.
Oh wait You don’t believe me. Let’s prove it.
My export must have 1941 lines (and should have a Row with all #Missing)
Nope I just have 1938 lines and nothing with all #Missing.
Nope no #Missing rows 🙂 (It’s strange I know, it think it is bug which happen to creep into from 18.104.22.168.501 – a good bug)
Did I prove Glenn wrong (no I didn’t), however I like to think that I did so that I can complete a virtuous cycle (Glenn torturing Cameron, him torturing me and if and only if I can torture Glenn). Well that’s lot of an ask 🙂 and lot going on