Timing Setings for an Variable (Datapipline Is Not persisted)
Dear All,
How to overcome the problem that DataPipeline is not persistet after being
set
in a Timing Setting Dialog for an Variable?
Dialog has 4 ComboBoxes:
1.Calculate On
2.Reset On
3.DataPipeline
4. Reset On.
All setings stay, except DataPipline.
Thank you
Oleg Chtelmakh
How to overcome the problem that DataPipeline is not persistet after being
set
in a Timing Setting Dialog for an Variable?
Dialog has 4 ComboBoxes:
1.Calculate On
2.Reset On
3.DataPipeline
4. Reset On.
All setings stay, except DataPipline.
Thank you
Oleg Chtelmakh
This discussion has been closed.
Comments
When is the DataPipeline field changing? In my testing the DataPipeline
field is remaining set when I execute a report. I recommend you use the
Traversal setting rather than the DataPipeline Traversal setting so the
variable will only reset or caclulate once per record. The DataPipeline
Traversal setting supports moving forward and backward in the dataset so you
my not get the results you are after using this.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com