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 and Dynamic Parameters
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
LynneB
Past 24 Hours:
1
Prev. 24 Hours:
2
Overall:
5123
People Online:
Visitors:
161
Members:
0
Total:
161
Online Now:
New Topics
Lawson S3 Financials
PO Matched Dollars and Matched Quantity
5/10/2024 6:51 PM
Can anyone share the Lawson calculation to determi
S3 Customization/Development
COBOL CSV file
5/10/2024 2:36 PM
We have a custom Cobol program ZU200 that creates
S3 Systems Administration
Using MFA for Lawson S3 Access
5/8/2024 1:23 PM
Does anyone use Multi Factor Authentication when u
Lawson Landmark
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
IPA/ProcessFlow
Executing IPA from PR160
5/3/2024 2:46 PM
We're facing a situation where we need to upda
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1357
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson Business Intelligence/Reporting/Crystal
LBI and Dynamic Parameters
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
thummel1
Veteran Member
Posts: 121
9/5/2014 6:33 PM
Hi, I am using Crystal reports 2008. My Crystal report has 3 dynamic parameters. This allows the end user to select 3 separate critera (Job Class, Payroll Year, and Provider Comp Plan). In Crystal, the end-user can choose one or many job classes, one or many years, and one or of many Provider Comp Plans. When I publish this report to LBI, my parameters do not display the "left" "right" boxes that allow you move data from the left to the right that you want to include.
My question is, why aren't my parameters appearing just like they do in Crystal? I am puzzled. Thank you for your assistance!
Tania
Dave Curtis
Veteran Member
Posts: 136
9/6/2014 12:09 AM
When you publish to LBI are you selecting the use crystal report parameters option under the parameters? The default is the LBI parameter setup, I think if you switch it to the crystal report parameter setting, then you will see the difference.
thummel1
Veteran Member
Posts: 121
9/8/2014 2:15 PM
Hi and thank you. Yes this did allow the parameters to prompt; however, before I get there the system is asking me to enter my ODBC User ID and password. Another co-worker has run into this before as well. I did put in my User ID and password in the data Settings under Default User Id and Default Password. That does not stop the user ID and password screen from prompting; however. So whether I've entered the User ID and passsword or not under data settings, I still ge tthe User ID and password prompt. But once I enter it there, I do get the parameters screen to appear (which appears correctly.). How can I get the User ID and password screen to stop prompting now?
Dave Curtis
Veteran Member
Posts: 136
9/9/2014 8:12 AM
I have only seen this issue related to a few things;
1.User ID and/or password is/are entered incorrectly
- re-enter and verify username and password
2.DSN in LBI does not match DSN in report.
- in the data settings, select the LBI DSN to use
- OR rename DSN to match (either on Lawson side or report)
3.Something has been corrupted within the report
- publish a new version and test
I am sure I am missing some possible causes, but these have been the causes I have experienced.
mikeP
Veteran Member
Posts: 151
9/9/2014 12:47 PM
We have ODBC data sources set up in LBI that appear in Report Details, Data Settings in the Override Datasource list. They are created and maintained in Reporting Services Administration, New Data Source and Maintain Data Sources. They are configured with the name and password of a dedicated LBI database user with "read" rights.
When we publish a report, the default datasource is "Use report data source", which is the datasource name from the PC where the report was created that's stored in the report. Part of the publishing/republishing process is to set the override datasource to the one created in LBI that has the stored name and password. If we do not set the override datasource, we've seen different errors depending on the datasource in the report.
We'd see that name and password prompt you're getting back on when our Lawson database was on the iSeries DB2. Now we're on SQL Server, and we see "The viewer could not process an event. Failed to open the connection. Failed to open the connection", though the difference in errors could be due to different LBI versions.
This is a longwinded way of saying you may need to set a datasource after you publish or republish a report.
thummel1
Veteran Member
Posts: 121
9/9/2014 3:45 PM
Hi, yes, I just needed to enter the data settings correclty. Apparently this is an issue when there are dynamic parameters set up in the report. I changed the "Override Data Source" to "Use Report Data Source". I left the Default User ID blank, then I entered my Default Password and the confirm password. Under "When Viewing Report" I selected Use the User ID and password Entered above". Thi has resolved this issue. Thank you everyone!
You are not authorized to post a reply.