Prev
Next
Forums Performance Management Lawson Business Intelligence/Reporting/Crystal

Report Not Bursting As Expected

 1 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Elizabeth Ardito
Advanced Member
Posts: 34
Advanced Member
4/4/2014 1:50 PM
    I have been using LBI to published back office reports for years. We recently purchased the full version and I am attempting to setup and burst a crystal report with department data and vice president summaries (the summaries are subreports). We are on LBI version 9.0.4.2.

    The problem is, it seems to burst almost correctly. I only have access to the departments I am assigned to in the maintain rights but I have access to the vice president summaries who are responsible for the departments. The field that I am using for bursting is not on the summaries, although the department is listing. The data on the summaries comes from a different datasource than the main report and they are linked by the vice president.

    I have opened an incident with Lawson but so far have not been able to give me an answer. They are currently looking at the crystal report.

    First question: is my thinking that if the bursting 'tag' is not on a portion of the report, then you should not have access to it?

    Second question: any suggestions as to why this might not be working?

    Any assistance is greatly appreciated!

    Thank you

    elizabeth



    thummel1
    Veteran Member
    Posts: 121
    Veteran Member
    7/23/2014 11:07 AM
      I am curious to know if you received a solution to this issue? I, too, have a report that I need to burst to each manager that contains subreports (5 subreports to be exact). My report is supposed to burst on the manager's UserID (which is in the "main" report). In LBI, I have this report set up on a schedule, set to burst on this UserID Data Field. Lawson Support reviewed this with me yesterday. They said I need to bring in the UserID to all the subreports as well. So I did that, created a shared variable within each one, and brought the UserID into my main report. Still the report doesn't want to burst. My issue is that I get a prompt for a User ID and Password. If you found a solution that works for you I'd love if you could share!