First question is why export? Don't spend a lot of time hunting down a fix for known system behavior if this isn't a true requirement. Using OBIEE as the mechanism is terribly inefficient when you need data dumps to feed internal/external systems.
BUT - is your column in the criteria AND the filter or just filter? This might lead you to 'removing' it from the export if it isn't in the criteria (you'll need it for the filter to still have the drill work)
on export, I could not agree with you more, but since when do end users listen to us...
On the criteria, this is classic action link where the end user clicks on a value in the source report and this 'throws' parameters that are 'caught' by filters (is prompted typically, though also presentation variables)
thanks for your input Thomas.
I'm thinking that the dump includes ALL criteria columns ... if the purpose is filter only, try just having the column in the filter on the advanced tab and not in the criteria tab.
Hello again Thomas,
the columns need to be in both filter and display columns.
I have noticed that the side effect only happens on larger data volumes, could this be related to configured limits on streams / java heap etc?