Note: using 2009.1 stable. not attempted on new preview release.
When I save a report the GetPreviewDataSet event appears to be fired before the SaveReport event. This is very unexpected and undesirable behavior, I would expect that only the SaveReport event should fire when I save a report. Was this intentional, or possibly a bug? Is there a way I can check to see if GetPreviewDataSet was thrown due to the save button, or a request for a preview so that I can skip the processing in the event handler.
Thanks for your time.
Clicking Save in the designer first throws the GetPreviewDataSet event.
Clicking Save in the designer first throws the GetPreviewDataSet event.
Does anybody know anything about this? Is this a known issue, or possibly something I am implementing incorrectly? Can anyone reproduce the behavior? Unfortunately until I have a resolution or a work around I can not implement the preview functionality that I need, which is not sitting very well with my employer.
Clicking Save in the designer first throws the GetPreviewDataSet event.
Hi
You are right. Release version 2009.1 contains this bug.
We corrected it later. So please download the latest available prerelease build with a correct order of the events firing.
Thank you.
You are right. Release version 2009.1 contains this bug.
We corrected it later. So please download the latest available prerelease build with a correct order of the events firing.
Thank you.