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!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, November 6, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders