Dynamic Parameter Asking for Login Information

[GregT27]

Is there a way to prevent Crystal Reports 2020 asking for login information for dynamic parameters?

Our users use the report via a viewer that our ERP system uses. It passes along the login.

[DonWilliams]

Hi Greg,

Ah, FireDAC must have a Client Database connector that CR uses to connect to it.

CR 2016 is a 32 bit application and CR 2020 is a 64 bit application so it requires a 64 bit Client.

The way CR works is when the DB connection is made CR stores the log on info in memory and releases the connection so the Client doesn't get hit with potentially 100's of connection requests. Normal behaviour...

I suspect what FireDAC is doing is releasing the connection, so each CR parameter will open the connection to pass the parameter to the Client/DB. FireDAC appears to be closing each connection. Because CR Parameters must be set before the connection is made, it's like a Stored Procedure with parameters, the value must be set before the log on info is attempted.

If you enable CRLogger, KBA 1603398 - How to trace data source connections in Crystal Reports using crlogger? [Video]

The log file may show what is happening...

I suggest contacting FireDAC support and ask them if they have a 64 bit Client or if they could have a look at your issue, the log file may help them determine what is happening and why the connection is lost every time a refresh is completed.

Nothing in CR configuration to make this work, no difference between CR 2016 and CR 2020 has changed for this work flow...

Don

[DonWilliams]

No, not by default. CR will never retain passwords, huge security breach if anyone can access the data source, they could modify the report and access data they should not be able to see....

Talk to your ERP Administrator, they may be able to set the password for you depending on how they have implemented the reports. It is possible to set the log in info so it doesn't prompt but that all depends on how they have implemented the report security.

You can set the log on info in the report to use Trusted Authentication which should use the initial log on info when the report is saved. Refreshing with a new value should then use the existing DB connection info.

PS - If you are using Business One ERP system add the Business One Tag.

[GregT27]

Hello.

I am the ERP Administrator.

When the report is launched in the designer, it connects to the database  with the credentials that I enter. I get a prompt again to reenter it each time for the dynamic parameter.

CR 2016 did not require a login for dynamic parameters.

Thank you for the information about the tags. We are not using Business One.

[DonWilliams]

CR can use a default DB log on info, I suspect the Client has changed. When the report is opened Verify the database and save it and see if that fixes the problem. What Client are you using? ODBC, OLE DB or???

[GregT27]

I did the database verification and resaved it. When I open it I get the normail login request but I still get the second request for the parameter. If I remove the parameter then I do not get the second request.

[DonWilliams]

Thanks for testing. Need more details, How are you connecting to your DB, ODBC, OLE DB or???? What version of the Client is it?

[GregT27]

The connection done via FireDAC. It is a requirement with our ERP software. I created a report in CR 2016 and I did not have this issue.