megaphone
SuiteWorld 2026 registration is now open—save $300 Register now
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.
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!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Don't miss out on our Pop Quiz! You only have until tomorrow, June 19, 2026, 7:00PM ET to comment your answers.
What if your ERP could help surface the next step before you go looking for it? Watch here to learn more!

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.
Save $300 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover 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. Register now

Syntax issue?

edited Jan 3, 2020 12:27AM in Search / Reporting 3 comments

When introducing a new string to a formula we ended up dropping income values of certain transactions. The new string's purpose is to eliminate transactions double posting due to a script that runs on our invoices.

I need help to identify if the second set of formula are written incorrectly, or if any glaring issues appear to anyone.

The original formulae:
to_char({debitamount},'9999999.99')
and:
to_char(({creditamount}*-1),'9999999.99')

The revisions:
CASE WHEN ({account.custrecord_house_account} = 'T' AND {debitamount} IS NOT NULL) THEN '0.00' ELSE to_char({debitamount},'9999999.99') END
and:
CASE WHEN ({account.custrecord_house_account} = 'T' AND {creditamount} is not null) THEN '0.00' ELSE to_char(({creditamount}*-1),'9999999.99') END

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 2 (Apr-Jun 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders