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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
ODBC SQL bug? nextline filter is not filtering
I work with Netsuite2.com ODBC Suite Analytics Connect
I run the following SQL Query
select ptll.linktype, ptll.nextdoc, ptll.nextline, ptll.previousdoc, ptll.previousline
from PreviousTransactionLineLink ptll
where nexttype = 'VendPymt' and linktype = 'Payment' and previoustype = 'VendBill'
and ptll.nextline >1
But it still leaves the line with nextline=1 in the results although I specified ">1" in the where clause.
I have checked also the tables: PreviousTransactionAccountingLineLink, NextTransactionLineLink, and NextTransactionAccountingLineLink, they all have the same bug
Interesting that transactionline table acts OK
Is this a bug? Do I miss something?
Tagged:
0