Question Re: Salesforce ODBC driver does not return data in Technology Q&A

Salesforce ODBC driver does not return data

dave_smith2 — Thu, 12 Dec 2019 20:36:25 GMT

We are using the SAP Crystal runtime for .NET SP 24 32 bit (v13.0.24.2970) and attempting to connect to a Salesforce data source.

Unfortunately, we keep getting the could not load database information error and it appears that the runtime does not support the native Salesforce driver (see https://answers.sap.com/questions/9443299/connecting-to-salesforce-via-the-crystal-runtime-f.html).

As a workaround, we tried to modify the reports to use ODBC instead, connecting via the built in SAP Salesforce ODBC driver that gets installed with SAP Crystal Reports 2016 SP 7 (Simba Technologies v2.00.19.1019). The reports would either not find mapped fields or if they did, would not return any data whereas the same reports would run properly using the native driver.

Is anyone aware of any solution to this problem? I believe if we can get the reports to work using ODBC then our application would be able to execute them through the runtime.

Re: Salesforce ODBC driver does not return data

vitaly_izmaylov — Fri, 13 Dec 2019 20:40:27 GMT

Look at

https://apps.support.sap.com/sap/support/knowledge/public/en/2245135

Note to access any KBA for Crystal Reports use Public URL:

https://apps.support.sap.com/sap/support/knowledge/public/en/

and add the KBA number

Re: Salesforce ODBC driver does not return data

dave_smith2 — Fri, 13 Dec 2019 21:26:18 GMT

Hi Vitaly,

Thanks for the response.

Yes, we are familiar with that KBA and have reviewed it, but none of issues covered are relevant to our situation.

The only way this works with the Crystal .NET runtime is to use the Crystal 2008 SF dlls and go through that framework. Updating to 13.0.24 completely breaks the ability to execute reports to a SF data source using the native driver. And because none of the SF ODBC drivers work (I have tried Progress, DevART and even the newer Simba driver), we are stuck.

Will SAP provide native support for SalesForce data sources through the .NET runtime?

Re: Salesforce ODBC driver does not return data

vitaly_izmaylov — Fri, 13 Dec 2019 21:42:03 GMT

Have you tested those reports in SAP Crystal Reports 2016 SP 7 designer?

If yes, what is the error?

Re: Salesforce ODBC driver does not return data

dave_smith2 — Sat, 14 Dec 2019 00:00:27 GMT

Yes. When using the native SF driver, everything works as expected.

When trying to update the native driver with the shipped Simba ODBC driver, we either get errors indicating there are unmapped fields (primarily when referencing SF Reports or stored procedures) or no data being returned.

Re: Salesforce ODBC driver does not return data

vitaly_izmaylov — Mon, 16 Dec 2019 16:03:08 GMT

Strange, according to KBA 2247073 it should be resolved in the driver version you specified (v2.00.19.1019)

Can you create a brand new report of the same SF stored procedure using the ODBC driver?

Re: Salesforce ODBC driver does not return data

dave_smith2 — Mon, 16 Dec 2019 17:30:34 GMT

Yes, I was able to. The SF report came through as a stored procedure without any issues on a new report, but when I tried updating the existing report to use the ODBC connection, the unmapped fields error still popped up.

The bigger issue is the lack of data being returned. One particular report was successfully converted to ODBC, but did not return any data even though the same report using the native SF driver did.

Re: Salesforce ODBC driver does not return data

vitaly_izmaylov — Mon, 16 Dec 2019 20:09:50 GMT

You can compare the Field names, types and sizes of the original report and the new report of the same stored procedure in Field Explorer (right-click Database Fields and check "Show Field type")

If there is a difference it would explain why you are prompted to map fields.

You know it would be easy just to copy all sections from one report to new one and report will be recreated

Re: Salesforce ODBC driver does not return data

vitaly_izmaylov — Mon, 16 Dec 2019 20:09:51 GMT

You can compare the Field names, types and sizes of the original report and the new report of the same stored procedure in Field Explorer (right-click Database Fields and check "Show Field type")

If there is a difference it would explain why you are prompted to map fields.

You know it would be easy just to copy all sections from one report to new one and report will be recreated