Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Performance Management
Lawson Business Intelligence/Reporting/Crystal
LBI/Crystal XI Failure to Process Prompt Error with Cascading Parameters
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
1
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
48
Members:
0
Total:
48
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Performance Management
Lawson Business Intelligence/Reporting/Crystal
LBI/Crystal XI Failure to Process Prompt Error with Cascading Parameters
Please
login
to post a reply.
2 Replies
0
Subscribed to this topic
24 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Charlotte Chase
Basic Member
Posts: 8
7/17/2009 12:55 PM
I have a Crystal XI report with a cascading parameter. The report uses a SQL command rather than a stored procedure. Runs fine in Crystal, but when published in LBI the first prompt works, but I get a "Fail to process prompting" error on the second parameter. If I get rid of the SQL command and pull in the tables directly, both parameters work in LBI, but that just kills performance. Has anyone had experience with this? Thx!
Char
Veteran Member
Posts: 62
New Poster
Congrats on posting!
7/17/2009 5:41 PM
Split
Charlotte:
Strangely enough, Charlotte here too. I have a client where I use XIR2 but one of the folks in accounting had this issue running one of my reports from Crystal Reports on a Crystal XI R1 machine that had no patches, I had him upgrade to XIR2 and he stopped getting the error. While it didn't happen on LBI, I know for a fact that LBI is R2 suggesting that a patch might be in order (or upgrade to R2 which is probably just as good if not better). Hope that helps!
Char
Charlotte Chase
Basic Member
Posts: 8
7/23/2009 8:03 PM
Split
A belated thanks, Char. I will run it by my client. That is the only recommendation I've heard.
Please
login
to post a reply.