|
|||||||||
|
Crystal Reports Tools: Improve Performance While Saving Time and Money |
|
Crystal Reports: Exporting Memo Fields to Excel or CSVA Chelsea Technologies client report had a table with a memo field with several lines of data in the field. When we exported from Crystal Reports 2008 to Excel Data, the field value was ignored. In Crystal Reports 10, we got all the text from the field, but with the CR/LF characters removed. Neither was what the client wanted. Our Grid User Function Library helped develop a solution here. It is a powerful and cost effective solution to extract data from your report into a structured format like CSV or tab delimited data. This example creates a CSV file with three columns (Record ID, Name and Memo Field), with field names in the first row. It also assumes that there is on average, 10 lines per memo field. Increase this if you have lots of lines in your field. The {@ClearGrid} formula goes in the Report Header section:
Place the Page N of M special field in the page footer to force the processing of all pages, and every time you view or refresh the report, the file will be recreated. You can also export part of a report: Export part of your report using a UFL The report looked great. It had many pages showing each of the invoices prepared over the previous month. These were exported to a PDF and sent to a document management company for storage. But then came the challenge. We needed a second document to list each invoice and page number of the master documents they appeared on. Our collection of User Function Libraries came to the rescue. Using these inside a formula can create a disk file while the report is processing.
As they are all "WhilePrintingRecords" formulas, they can accurately include information such as the page number and print time. Now, here's something else to consider. If you are exporting data, there's a fundamental problem. Either your report users like to waste time, or you are delivering formatted data instead of business intelligence. You need to ensure your reports contain business information, not business data. They need to be decision tools, not intermediary data sources. To get there, start by determining what business questions need answering. For example:
When people want to export data to Excel, they are usually attempting to answer questions not directly answered by the data. In the examples above, you would have to perform analysis in the report, using formulas and other tools available in the reporting software. The data approachThe normal approach is to start with the database and push data to the users. No matter how you dress up data, you still have data. You do not have information. Data are raw materials and information is a finished product. Suppose you walk into a Toyota dealer and say you need transportation. Do you expect to walk out of there with a container of parts, or to drive out of there in a car? That is the difference between data and information. When you shove data at people, they try to assemble the data into information. Which is why you have all these folks wasting millions of salary-hours manipulating spreadsheets instead of doing the jobs they are paid to do. Which is why you have information silos. Which is why you have all sorts of other problems, which is why your job is less secure than it should be. End-users need analysis, trends, conclusions, snapshots, summaries, thumbnails, overviews, projections, comparisons, and other things that are very different from data. When they don't have those things, out come the spreadsheets. The report approachInstead of starting with the database, start with the business questions. Talk with the senior executives (who may or may not be on your existing distribution list), and ask each one to tell you what the top three business questions are. If they give you more, that's OK. Compile a list, and see what data you would need for you to answer those questions with your reports. Next, repeat this process with the people who are already on your distribution list. You are now ready to determine what will be reported. Why talk with the senior executives, first? Those are the folks who run your company, so figure out what they want. Providing that helps secure your job and future raises in no small way. But it also helps you build the correct framework for your entire process, so that all users are marching to the same tune. You have to start at the beginning, not in the middle. By definition, middle managers can't see the big picture. This raises another point. Surveys conducted between 2005 and 2008 showed that senior executives rarely have an accurate picture of their organization or the conditions under which it operates. They have a much rosier view, because people generally try to please them. These same people lack the time to dig through the data to see the real picture. In most companies, senior executives also lack the skills to do so. This means the data-oriented reports they get are essentially useless. If you are in charge of those reports, what does this say about your value to the company? If you provide the senior executives with the business information they need, and you provide middle managers with the business information they need plus the business information the senior executives are working from, how do you think this will affect the effectiveness of management to make good decisions? Instead of working from the detail level up, work from the information level down. Determine what information people really need. Then, use the power of Crystal Reports to assemble that information from the data you can get.
This article is copyrighted by Crystalkeen, Mindconnection, and Chelsea Technologies Ltd. It may be freely copied and distributed as long as the original copyright is displayed and no modifications are made to this material. Extracts are permitted. The names Crystal Reports and Seagate Info are trademarks owned by Business Objects. |