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
FAM Update Broke System-Generated Journal Entry Identification — Workflow Issue
Hi everyone,
We’ve run into an issue after the latest Fixed Assets Management (FAM) bundle update and wondering if others are seeing the same:
Problem:
We have a Journal Entry Approval workflow that automatically approves system-generated journal entries, based on this condition:
{custworkflow_created_by.id} = -4
Previously, journal entries generated by FAM processes like Depreciation had created_by = -4, so they were auto-approved as intended.
Since the recent FAM update:
- Depreciation Journal Entries are now showing the actual user or integration ID under
created_by, instead of-4. - These journal entries are now being sent to manual approval by our workflow, which isn’t the expected behavior.
0