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
Historical Report Instance and bursting
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
NonnieBear1776
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5162
People Online:
Visitors:
251
Members:
0
Total:
251
Online Now:
New Topics
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
1348
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
Historical Report Instance and bursting
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
James Deno
New Member
Posts: 4
9/25/2013 8:53 PM
I'm wondering if someone could help me to understand how bursting works when applied to a historical instance of a report. I have a crystal report that is bursted based a field in the report (user ID) so they can view their page only. The bursting works fine when you select "view the latest instance", however, once a historical instance is created from the scheduler, it prompts for a user ID and password. If you enter the UID and password at the prompt, it opens the report, but managers aren't going to be asked to enter those credentials.
I have saved the user ID and password at the data source selection, when published and selected "use the user ID and password entered above" but it still asks for the info before it displays the report.
Does a historical instance require different settings for bursting security? As far as i can tell, I've configured everything correctly and selected burst in the schedule manager and in the bursting set up.
Greg Moeller
Veteran Member
Posts: 1498
10/4/2013 2:56 PM
What type of file are you talking about when you say historical instance? A rpt file, pdf, xls?
pdf's seem to have the bursting and security built into them as they are produced.
Greg Dey
Advanced Member
Posts: 23
10/4/2013 4:14 PM
I am running 9.0.4.2 and bursting does not work for me when scheduling the report (although I don't recall how the problem manifested itself). I am creating historical reports in pdf. If I manually create the historical report the bursting works fine. At the time I logged an incident with Infor support and they tested 10.0 and it didn't burst at all. I decided I would wait to upgrade. My workaround has been to use me as the scheduler.
Greg Moeller
Veteran Member
Posts: 1498
10/7/2013 3:10 PM
I thought that we had run into similar issues with bursting and 9.0.4.2 as well. The current version of LBI 10 seems to work much better.
You are not authorized to post a reply.