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.
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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Error: "DHRS_NOT_FOUND: No depreciation schedule records found" during FAM Asset Depreciation
Hello,
we ran FAM Asset Depreciation and we received following error: Error: "DHRS_NOT_FOUND: No depreciation schedule records found" during FAM Asset Depreciation.
Based on the Answer Id: 81138 user manually sets the Asset Status to Fully Depreciated but the Depreciation Active field is set to True.
I've ran multiple searches to see if such change was performed recently checking the system notes on FAM Assets however such change was done by user in 2021 but the depreciation process before was finished without any errors before.
Also the users do not recall performing such change recently.
Could you please advise if this change from 2021 could trigger such error now and why would that be?
0