Bursting applied to historical instance of crystal report

I have a crystal report that is bursted based a field in the report (user ID) so the user 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.

Find more posts tagged with

Comments

Legacy Contributor

Are you republishing the report each month because you have to change the dates or something else in the report. Is so, you have to enter the user ID and password again on the setup page

Legacy Contributor

No, I am not republishing the report. We just want managers to be using a historical instance of the report to minimize any performance issues related to number of users pulling a report with data refresh. Right now, I just have a manager testing the report.

So it's just a scheduled, bi-weekly report. Hope that made sense....

Legacy Contributor

Yes that makes sense. That is only thing I could think of that makes link to security source data break. We have been bursting for years, but we republish each month because of data date changes that have to be reset in the crystal report so it works in LBI bursting (which now that I type that may be an issue that has been fixed and I submitted to Lawson; I have never tested again - duh - which I will do - thanks for heads up to me with your question!)

Legacy Contributor

I had a similar problem. It worked properly upon View with Data Refresh, but historical instances would prompt for user id and pw.

Historical instances only worked for me after I replaced all the tables with a single sql command - making sure that each field was uniquely named. (ie. I did not leave two different fields both named 'Description').

Legacy Contributor

You also have to make sure the field you are bursting on is actually on the report. It can be suppressed, but if the field is not brought over from the field explorer onto the design of the report, crystal will not fetch the data for the field when the scheduled instance is created. It tries to go back out to the database to get that information, invoking the login prompt.

Copyright © 2025 Infor. All rights reserved.