Using infoset based on logical database gives lots of selection parameters

[Former Member]

Hi

I'm trying to assist a new Crystal user in getting up on running on Crystal using infosets from SAP. Presently a simple infoset based on logical database PNPCE has been built using fields from just three infotypes (to keep things simple).

When the user logs onto crystal and selects either this infoset, or a query based on the infoset, the very next step requires the user to set 80+ parameters to be null before running the report, and unfortunately those values cannot be saved to if in order to re-run the user has to manually set all the vallues to null again. Clearly this makes it pretty frustrating to use!

This initial screen does not appear if using an infoset based on table joins, but unfortunately the logical database needs to be used to fulfill certain reporting requirements.

I've tried saving a selection variant against a query and forcing it's use but these setting don't seem to be picked up by Crystal.

Are there any Crystal/Query experts out there that can help with this?

Regards

Phil

[former_member11696]

Crystal Reports is a Relation Database Reporting tool. If you can't link the tables then you'll have to use subreports.

[Former Member]

Hi,

Is there anyone out there that can help with this? Seems to me like an issue that there 'should' be a soluton to...but I haven't found it yet!

As a bit of additional info - the use of table join based infosets is not an option primarily because there are a lot of reports required that pull in the OM 'additional fields' that come through automatically when using an LDB. However, for table joins, it requires custom coding to be required to the infoset, which clearly restricts the user base from the ability to build their own reports.

Regards

Phil