SAP Knowledge Base Article - Public

2363553 - PostgreSQL Boolean field displays as a string in Crystal Reports 2013 and below, but as Boolean in Crystal Reports 2016

Symptom

  • Field data type different in Crystal Reports 2016.
  • Boolean field set to display as a string, shows as boolean in Crystal Reports 2016.
  • When updating a report created in Crystal Reports 2013 and below, based off PostgreSQL, it generates error in formula due to incorrect data type.
  • PostgreSQL Boolean fields displays as a String data type in Crystal Reports 2013 and below, when the PostgreSQL ODBC Driver option: “Bools as Char” is checked, but shows as a Boolean data type in Crystal Reports 2016.

Environment

  • SAP Crystal Reports 2016

Reproducing the Issue

  1. In Microsoft ODBC Administrator, create an ODBC DSN for a PostgreSQL data source.
  2. Check the option: "Bools as Char": to convert Boolean Field as string field.
  3. In Crystal Reports 2016, create a report off PostgreSQL using the ODBC connection.
  4. Select to add the table containing boolean value field.
  5. Check the data type displayed for the boolean filed.
        
    Notice, it displays the Boolean fields as Boolean and not as string, therefore it does not respect the option defined on the ODBC DSN.

Cause

  • This issue have been traked under SAP Note 2343622

Resolution

  • The issue is planned to be resolved in the following product update and above:
         
    • Crystal Reports 2016:
      • Support Pack 04

Keywords

CR, Bool , KBA , BI-RA-CR , Crystal Reports designer or BusinessViews Manager , Bug Filed

Product

SAP Crystal Reports 2016