megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

ODBC Data Types

edited Dec 3, 2019 3:46PM in SuiteCloud / Customization

Hi,
I'm just wondering if anyone else has come across any data type issues when using ODBC (driver version 7.02.00.54).

The issue that we're having is that none of the data types are being recognised correctly across any of the applications that we use which use the system DSN created during the ODBC setup process.

All fields are either coming through as either nvarchar(4000) or float and nothing matches the data types specified in the connect schema documentation.

Is there a way to configure the codepages or data types of the ODBC connection itself as no amount of tweaking source/input/output properties in applications such as SSIS will change them and we are presently having to convert all data at the time of extraction from the odbc source which is impacting performance and unnecessarily complicating our ETL processes.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders