LBI report prompt for username and password

Maybe some background will help, going from memory...

IIRC, LBI prompts for name and password when there is no name and password stored with the datasource. We have datasources created in LBI that have been configured with a stored user and password; this was actually done by Lawson managed services, they run our servers. Every time we publish or republish, the report's datasource allways reverts to (I paraphrase, don't have access to the server right now): "Use the data source stored in the report" which is the datasource on the PC used when the report was created. So every time we publish or republish, we need to set the report's datasource in LBI to the LBI datasource, which overrides the datasource stored in the report.

If the report is run without overriding the datasource, one of two things happens:

If the report was developed on a PC using a system DSN with the exact same name as a system DSN that's been configured on the LBI server, LBI prompts for username and password.

If the report was developed on a PC using some other DSN, LBI displays a message similar to "Failed to open the connection."

Hi,

I had a similar experience recently. I re-published an existing report with a slight change in the Record Selection formula and after publishing to LBI and populating the user name and password in Data Settings, I tried viewing the latest instance of the report, and it would trigger the prompt for user name and password even though this was already pre-populated in “Data Settings.” However, as you seem to indicate the report ran successfully when run with Data Refresh. I have not quite figured out how that worked? I tried a couple of things: One was run the report without bursting to see if it ran successfully without the prompt appearing. In my case it did run without the prompt.
I re-checked the data structure and data elements to ensure they were working properly, and they appeared to be working fine.

After a process of elimination, the discovery of the problem was that it was not isolated to the bursting issue; it had to do with the Record Selection formula. For some reason LBI did not like the Crystal Record Selection formula. But, when I copied the exact same formula from the Crystal editor to LBI “customize selection formula" screen and pasted it there and turned back on the bursting and tried viewing the latest instance, the report ran fine without the prompt.

The conclusion was that and as confirmed by Lawson Support is that it is a bug in version 9-0-4-1-150. They further indicated that the next version had this fixed. We have not still upgraded to the newer version, so I cannot confirm this as a fact.

If you happen to be on the same version as we currently are, then there is a good possibility that you have hit the bug :-). If may like to try what I did and see if that works. But, If you are on a later version, then it may be something different.

Just thought I will share my discovery of this same debacle you seem to be experiencing.

Regards,
Imtiaz.