My Stuff
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.
Comments
-
Hi @Kevenale A Transaction Saved Search might be right approach here. There is a NetSuite Answer ID 89639 that walks through building a GP saved search, but it will need a few adjustments for your use case: Transaction Types: Include all relevant types (Invoice, Credit Memo, Vendor Bill, Vendor Credit) not just Invoices…
-
Hi @User_S8PAJ Can you check how your integration is setting the shipping address? Specifically: Why is it setting the Override checkbox? Is it populating the structured address fields (addr1, city, state, zip) or just the free form addrtext field?
-
Hello @Didik_Rohadi Could you clarify a few things: What is the source transaction type (e.g., vendor bill, prepaid expense, journal entry)? What exactly needs to be revised: the amount, account, date range, or something else? Are the amortization JEs already posted, or still unposted/pending?
-
Hello @User_G88KI A few things to check: TBA is no longer supported in SuiteCloud CLI v3+. If you're passing NS_TOKEN_ID and NS_TOKEN_SECRET, that's your problem. You need OAuth 2.0 M2M authentication. Your deploy step is missing the required environment variables. Every step that touches NetSuite needs both…
-
Hi @User_W8HUT That sounds like it could be a caching glitch or an issue with how the workflow evaluates under certain conditions. Since they were editing in the UI, did you happen to ask the user exactly what steps they took to make the edit? It would also help to know if your lock logic is using a standard workflow…
-
Hi @Richard Appleford OB If your custom role already has Full permissions for Sales Orders, the issue is likely a custom script or workflow throwing an error in the background during the CREATE/EDIT event, rather than a standard NetSuite permission blocker. A few ways to narrow this down: Check Script Execution Logs: Try…
-
Hi @User_K51C7 if you want to go the technical route, you can just use a User Event Script to automate this. You’d use the Before Submit Function event to compare Old Record vs New Record. Just subtract the old quantity from the new one and have the script set the value in your custom transaction line field. it works…