# Seeing NULL data points where there should be dates?

**URL:** <https://community.cdata.com/t/seeing-null-data-points-where-there-should-be-dates/225>\
**Category:** CData Drivers\
**Tags:** discussion, netsuite, suiteql, null\
**Created:** [June 28, 2023, 9:28pm UTC](https://community.cdata.com/t/seeing-null-data-points-where-there-should-be-dates/225 "2023-06-28T21:28:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Theo](https://avatars.discourse-cdn.com/v4/letter/t/a87d85/32.png) [@Theo](https://community.cdata.com/u/Theo)\
**Post date:** [June 28, 2023, 9:28pm UTC](https://community.cdata.com/t/seeing-null-data-points-where-there-should-be-dates/225/1 "2023-06-28T21:28:35Z")

</div>

When using a CData NetSuite connector&nbsp;for a NetSuite data source, you may encounter NULL data values that correspond to Date fields in your original data. This has been seen occurring when using&nbsp;the&nbsp;SuiteQL API in particular.

To remedy the situation, one solution is to use a TO\_DATE function in your SQL statement. For example, a field called “Purchase”.purchaseDate would be included in a manner such as the following:

TO\_DATE(“Purchase”.purchaseDate, ‘YYYY-MM-DD’) AS “purchase\_date”

where the date format and alias are adjustable based on your needs.