Data Item: How can I pass a parameter (e.g. orgname which is a field on the report) to the SQL.
Create Folder: Can I dynamically pick up the folder name from a defined data item.
I have the following msg from bursting schedule:
Basic syntax is not supported in group or record selection formula.[-2147189563]. My crystal report does have the org name as a group and I have also report bursting index on org name. I do not define a record selection in the report.
If I can define the destination directory from a database field then do I have to define each org in the 'group value' like 'Development Service' when setting up the report output.
Also the table list comes up without schema (I am using Oracle and the data I pulled can come from several schemas within the same database), will you eventually support native driver instead of going thru ODBC ?
- Data items are not used to pass a parameter value from CRD to the sql statement. They are used to collect information from the database. The information is then used by CRD. So, to pick up a parameter value FROM the database TO the report you would use the GUI to create a sql statement e.g select orgname from mytable where date = date().
- Yes. Place the cursor where you want thatvalue to be in the destination folder field, click "insert" and insert the data item.
- You are not setting up the bursting schedule correctly. I would suggest you log a call with the helpdesk. They will look at your schedule and your report and come back to you with some suggestions. You can log a call by going to Help - Support in CRD.
- Yes, you have to define a destination for each group. On the basis of this, I suspect that a dynamic schedule will be more the thing to use rather than a bursting schedule. Same end result, but you don't have to define individual destinations for each group manually. This is done by SQL and therefore requires little maintenance and updating if group names change, or new ones are added.
- You will have to ask CRD support about this, but I think you are getting confused with CRD and Crystal. Crystal's native connectivity is for Crystal reports and CRD will use Crystal's native connectivity to run reports which have been written in this way. CRD, like any other third party application, communicates with databases through ODBC drivers. I doubt ChristianSteven are planning to write their own connectivity modules to specified database types... there aren't many companies that do this as the ODBC layer is what is universally recognized as the methd of communication with databases. But it won't hurt to ask the question.
Do let me know what they say, and how you get on with your bursting schedule problem.
