Report Specifications 2

[makk07]

Hi Everyone,

I am new to the reporting world,please help me out.

I would like to know what are the steps involved in creating report specifications? OR When the end-user ask you to build a report what are the questions I should ask him?

Thanks!

 

[synapsevampire]

Ask them to provide a mock up example in Excel or whatever program so that you can visually see what they want, and get sign off on that.

Determine how the report is to be run:

scheduled vs. on demand?
format (Excel, PDF, Crystal, or?)?
emailed, printed, or?
what data source is used?

Will there be parameters passed to filter the data? Such as date ranges, geographic information, etc.

That should handle the basics.

-k

 

[scooterny]

Remember to look at the user specifications with a critical eye. Just because the user wants something doesn't mean it can be done or is practical to do. Take the specs back to your desk and go through it step by step to make sure it CAN be done! Write down all of your questions - Where do I get the data, do I have access, is CR the best tool for the job at my disposal, what is the time frame I am being given to get this done, is that time frame reasonable ( based on your experience ), remember to add a fudge factor in your time estimates, etc. Make sure you can answer your questions before you start the project ( or at least make sure the main ones are answered ). Then send a note to the user, copy whomever is important, saying as per your understanding, this is what you are agreeing to deliver, based on the users specs. Make sure they agree! Good luck.

 

[Madawc]

For Crystal, it's mostly a good idea to try things and see what works. This also means that most of the specification needs to be written after you have the code and as a record of the code.

There is also Export > Report Definition, not very user-friendly but better than nothing.

Madawc Williams (East Anglia, UK). Using Windows XP & Crystal 10