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
Disconnect between LBI role and right
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
5120
People Online:
Visitors:
338
Members:
0
Total:
338
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
1354
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
Disconnect between LBI role and right
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
imty
Advanced Member
Posts: 35
2/19/2013 6:29 PM
Hello group,
I published a Crystal Report in LBI and am trying to burst it by "Location." I have outlined in the attached document, screen shots of the steps taken in publishing this report in LBI.
The issue is that there appears to be a disconnect somewhere causing a hiccup. When I try running the report in LBI using "View with Data Refresh", it seems to work fine. However, when I try using View Latest Instance or try to run it from the dashboard link I am being prompted for a userid and a password which seems unusual and indicates to me that there may be some disconnect between the way the role and the right is established.
I would appreicate if you would kindly take a few minutes of your time and look at the attachment and see if you could decipher where the problem may be. I do not know what to check at this point to try to resolve this problem.
Thanks,
Imtiaz.
Matthew Nye
Veteran Member
Posts: 514
2/19/2013 6:41 PM
this is probably because the fields youre bursting on arent actually physically on the report. It also cannot be in a suppressed section of the report. Lawson explains it in KB 1187998:
"The reason this is necessary for historical instances is because you are viewing static data in historical instances as opposed to accessing the database directly when refreshing. If the field you are bursting on is not physically located on the report, then the historical instance will have no saved data to utilize from this field to burst on, as the only data saved will be from the fields that are physically located in the report."
imty
Advanced Member
Posts: 35
2/19/2013 7:02 PM
Thanks Matthew. I have the location grouping suppressed in my report. This is the highest level of the grouping and I am filtering on other attributes. So, the visible part the invoice field since this is the lowest level of the grouping. If I unsuppress the GH1(Location), would this help in bursting properly? Or does GF1 also have to be visible?
Matthew Nye
Veteran Member
Posts: 514
2/19/2013 7:11 PM
Header or footer, it wont matter, as long as all the fields you are bursting on are displayed some where on the report. You can still hide them by making the fields them selves the smallest possible width and height and then making then making the font the same color as the background. but they must print some where on the report.
imty
Advanced Member
Posts: 35
2/19/2013 7:37 PM
The suppression does not seem to be the issue. I unsuppressed the groupings and still I get prompted for a password and userid. It seems like the problem may be something else besides this. Any other thoughts or suggestions????
Matthew Nye
Veteran Member
Posts: 514
2/19/2013 7:45 PM
you made that change and ran a new historical instance? the old instances will still have the problem.
imty
Advanced Member
Posts: 35
2/19/2013 8:03 PM
I did run a new historical instance but I am still being prompted for the user id and password. If I re-type the user id and password again when prompted, then it runs. I am perplexed! I am wondering since I have several layers of grouping if this is causing the hiccup. For example, I am grouping by location,then by PO number, PO line number, UOM and Invoice. Could this be an issue with the bursting?
Matthew Nye
Veteran Member
Posts: 514
2/19/2013 9:16 PM
turn off bursting, run the report to create a historical instance and see if you get the login prompt. if so you know we're still dealing with a bursting issue. if not perhaps youve got a permissions issue (unable to view historical instance or something of that nature).
imty
Advanced Member
Posts: 35
2/19/2013 9:24 PM
Thanks Matthew. I'll try that and get back.
imty
Advanced Member
Posts: 35
2/19/2013 9:32 PM
I took off the bursting and ran a historical instance and it ran fine. I then did View latest Instance and it spat out everything. I then added the bursting and re-ran the report and tried running View Latest Instance and I get the prompt. I think the problem may be the Element to field mapping. This is the only thing I can think of. What are your thoughts. Where should I look?
Matthew Nye
Veteran Member
Posts: 514
2/19/2013 9:38 PM
hard to say at this point but it seems you are still dealing with the bursting mappings. id try using a more simplistic report or try the current report but simplify the bursting set up and try to isolate the offending element to field mapping.
imty
Advanced Member
Posts: 35
2/26/2013 11:02 PM
I was able to solve my dilemma. The problem was that I was using a field from the table rather than a field from the report as my bursting element. Dah! It took me a while to get this to work right. The error messages are not easy to follow for a mind as simple as mine. The only person in my opinion that can follow the error message is the person who programmed it. Asking Lawson support is worse yet, it is like the blind leading the blind.
Thanks guys for your suggestions. I will be back soon.
You are not authorized to post a reply.