Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
ODBC Data Types
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.