Dynamics Community Forum Thread Details

Custom Reports - Solomon ROI

Hi there. I have written a report that contains information from a couple of tables in SQL server, and I also have a connection to an iSeries database in the report. (Report was written in CrystalReports XI). I added this report to the Solomon ROI interface and whenever I try to run it, I get the following errors: CPREHLPR MFC Application has encountered a problem and needs to close. System Message 7011: ROI Get RIPARAM failed for CRPERC ERROR=. System Message 7011: ROI Get RIPARAM failed for CRPEMSGCNT ERROR=. I also created a report with only a connection to SQL server database and this one works without any issues. I'm sure it has something to do with my data source connecting to the iSeries. Am I not allowed to run a report through Solomon ROI that connects to something other than SQL server? Thanks for any help!

ROI will dynamically rewrite the SQL contained in the data source, based on the sort/select options that the user has entered onto the report screen. It also changes the database to the SL application database the user is currently in. For these reasons, accessing anything outside of the normal SL tables is a challenge. It is also why report patterns that need to execute stored procedures do so by first populating a temp table (wrk*) in the RunBefore or 'Pre' process that the report then runs against, witht he table being cleared out in the post process.

There are other problems that may cause this error:

1. You didn't mention which verison of SL this is. I don't think Crystal XI will work with any version prior to 7, and Crystal V10 may be the latest that works with SL 7.

2. If you are on version 7, there are also additional security considerations if running SL with Windows security.

Sugestions:

1. Make sur ethat this report is created in the same version of Crystal that came with your current SL version.

2. To access information on another server, your best bet would probably be to put that portion of the query into a view that is then referenced from Crystal. You may need to access the other data source by setting up a linked server in SQL Server that the view will pull from. There may be other issues with this - distributed queries are tricky to get working in an SL report.

3. If the view is not an appealing option, you might explore creating pre/post process stored procedures with a wrk table. This is a more complex reporting pattern to implement but can yield better performance. You also have more options as far as data processing within a stored procedure.

There is more information about how ROI works in these documents, which should be on your install CDs or CustomerSource:

SL V7: sl_roi.pdf
Solomon 6.5: SIV_RPTGD.pdf

Hope this helps.

Quick Links