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
Report will not burst
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Wayne Willis
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
5190
People Online:
Visitors:
199
Members:
0
Total:
199
Online Now:
New Topics
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
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
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
Report will not burst
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Donna
Veteran Member
Posts: 110
10/10/2017 7:27 PM
This is very strange. I have another version of the same report with the same bursting rights structure that runs successfully but the newly published report runs if I remove bursting rights but displays as a blank repot once bursting rights are added.
We even republished the report with a new report ID but it will not burst or even display any data once the bursting is added.
Jan
Veteran Member
Posts: 55
10/11/2017 1:10 PM
this is interesting - I'm having the exact same thing happen. I created a new bursting structure a few months ago and I've had an employee roster report using that and it has been working just fine for those two months. A couple of weeks ago, I published a new report using the same bursting structure, and it will not burst. I'm having I.T. look into this but so far they haven't come up with an answer. I've deleted and re-added the problem report to see if that solves anything, but it does not.
Has anyone else been running into this problem?
Anna F
New Member
Posts: 1
10/11/2017 3:20 PM
Hello Donna,
Long time! Try something: check your Record Selection area and if you have anything commented out - delete it. The bursting tags on and still looks at the commented out criteria as if it was not commented out.
republish it and test your bursting again.
Thanks
Anna
Dave Curtis
Veteran Member
Posts: 136
10/11/2017 3:50 PM
Honestly - we have odd issues like this occur occasionally and we will have something just stop working completely and have no reason why. Typically publishing a new version is what "fixes" the issue. However - it seems you have already tried that.
I know this may be a silly question - but do you have the bursting data point on your Crystal report? We have had reports not burst and we have had to put the data field on the report itself (not just in the data set). Even if it is a hidden field, it fixed the no bursting issue we had. Not sure that would be your issue but thought I would throw it out there.
Jan
Veteran Member
Posts: 55
10/11/2017 3:58 PM
Hi - thanks for the feedback. I do have the burst field in the report data.
However, I got my report to work by doing something very funky. I took a totally different bursted report that has been running for several years and gutted it - I deleted everything out of it. I then took the sql code out of my problem report and plugged that into the problem report, then I published that and burst it - and - it worked! I have no idea why though. Very strange.
Jan
Veteran Member
Posts: 55
10/11/2017 3:58 PM
Hi - thanks for the feedback. I do have the burst field in the report data.
However, I got my report to work by doing something very funky. I took a totally different bursted report that has been running for several years and gutted it - I deleted everything out of it. I then took the sql code out of my problem report and plugged that into the problem report, then I published that and burst it - and - it worked! I have no idea why though. Very strange.
NatalieD
Veteran Member
Posts: 53
10/11/2017 3:59 PM
I'm not sure if this is true, but I was taught to always make sure my bursted fields were groups in my Crystal report. We usually always burst our PO reports by Dist-Co and Acct-Unit so I make a habit of building my reports with those groups.
Donna
Veteran Member
Posts: 110
10/11/2017 8:09 PM
Thank you all for your suggestions. I will revisit the report and apply the new information to the analysis.
Donna
Veteran Member
Posts: 110
10/11/2017 9:15 PM
OK. The burst fields were goups.
Removed a comment from the report select - I never would have thought of that.
Republished it three times with different report IDs.
Tested the old report and it works so I copied it and modified it to meet the new report specs then published it to a new report ID and it still does not work.
I think I will do something else and try again tomorrow. I am at the point of bursting it in a Crystal report and emailing it.
You are not authorized to post a reply.