• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Integer field in Data Source

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Integer field in Data Source

    Hi,
    While building data sources on DB2 files with INTEGER data types, they appear as Binary. Is there a way to prevent this? PFA screen shot of the field that is actually an INTEGER field being shown as Binary.
    This is causing us some grief while joining the files.

    Valence version: 5.1.20171202.0.

    Regards,
    Pavan
    You do not have permission to view this gallery.
    This gallery has 1 photos.

  • #2
    Encountering same issue with BIGINT datatype too.

    Comment


    • #3
      Hi Pavan -

      We have replicated the issue and will be providing a fix on the next update. Thanks for the report.

      Comment


      • #4
        For now, maybe it would be best to create the data source by adding the SQL statement rather than going through the wizard.

        Comment


        • #5
          Hi Sean,
          Appreciate the response.

          Comment


          • #6
            Hi Guys,
            We have updated the CNX to 5.1.20180316 version and we were hoping that this would resolve the integer issue.(As per the change log in CNX forum, it should have been fixed in 20180221 version itself.
            However, on a SQL statement data source, we have an employee field(an integer), is still being recognized as a 4A. Unable to do a column filter or update on that field.
            Any help is appreciated.
            Regards,
            Pavan

            Comment


            • #7
              Hi Pavan,

              This issue has definitely been resolved. Did you resave the data source after you updated to the latest build? I believe you'd need to do that in order for the widget to know that the field in question is actually an integer and not a 4A field.

              If that doesn't work, please contact us on the support line and we'll have a look at it with you.

              Comment

              Working...
              X