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 Pop Quiz You only have until November 7, 2025, 2:00PM 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
Missing Transaction Accounting Lines in JDBC and SuiteQL SuiteLet
Hello,
Edit and update: It looks like the cutoff date is somewhere in March 24/25, 2023, which is when the 2023.1 release of Netsuite came out. Is that possibly related?
I am facing a strange issue querying Transaction Accounting Lines through both the SuiteQL suitelet and through the JDBC driver. I am using the latest JDBC driver (8.10.170).
When I query
select count(*) from transactionaccountingline where lastmodifieddate > to_date('2023-01-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss')
To get the count of all transaction accounting lines since 2023-01-01, I get about 228K results.
When I query
select count(*) from transactionaccountingline where lastmodifieddate <= to_date('2023-01-01 00:00:00', 'yyyy-mm-dd hh24:mi:ss')
0