Tigran Shahnazaryan · CEO @ Novelance · Gold Crown

Hey @Jeannie, I assume you are using it as part of SuitePeople, correct? I haven't used the time clock by Adi Insights. If you have the Manufacturing Module and need the time clock for the production, there is a native feature that might work better. NetSuite introduced the Timeclock feature in Manufacturing Mobile in the…

Changing the Status on the Opportunity for a Customer with "Customer - Current" shouldn't affect the Customer's existing status. You can test this in Sandbox or in Prod by creating a Test Customer and Opportunity.

Someone must have deleted them. You can create the required Customer Status via Setup → Sales → Customer Statuses. For the reference, these are the native Customer Statuses:

If you have an Opportunity for an existing customer (Status = "Closed - Won"), changing the "Status" to "Closed - Lost" (ID: 14) won't affect the Customer's status. There is also a status called "Lost Customer" (ID: 16), selecting which won't affect the Customer status either. When you have an Opportunity with a…

Hey @User_USGXE, Could you check the selected Accounting Preference for "Create and Maintain Revenue Element Upon Closed Order"? It is under Setup → Accounting → Accounting Preferences → General

Hey @Ben Belzer, Someone perhaps renamed the "Status" to "Customer Status" in your account. That's the field I am referring to (ID: entitystatus).

Hey @tech work, If you build a "Sent Email" Saved Search, it would show all messages sent to/from NetSuite. Are you also sending Text Messages from NetSuite? If yes, are you using a third-party solution for that?

Hey @Ben Belzer, The best practice is to select the "Closed - Lost" status on the Opportunity Record.

Hey @User_USGXE Could you check the selected Accounting Preference for "Create and Maintain Revenue Element Upon Closed Order"? If enabled, closing the Sales Order shouldn't impact RevRec. Also, could you clarify what you meant by "Usually the Revenue arrangement would update to replicate the partial billing"? Thanks.

Hey @Ivan Babiichuk, You might be able to do this via Item Saved Search and Transaction join. Here is an example:

Hey @User_FL4CK, This is only required if the "Inventory Status" (e.g., "Good", "Damaged") feature is enabled.

Hey @SanjeevV, Did you try to use another browser to see if you are getting the same error message? This is either a browser-related issue or a NetSuite defect.

NetSuite Saved Searches are extremely powerful; you can cover 80% of reporting needs using them. Still, there are unique requirements that a Saved Search alone can't satisfy. Correct, the Reports and Analytics won't work here.

Hey @Rachel_A, You can't achieve this with a Saved Search only. You would need to create a "Latest Invoice" checkbox on the Invoice record and a scheduled workflow to mark/unmark it regularly. Then, in your Saved Search, you would use the "Latest Invoice" = "True" combined with the required date range to show the required…

Hey @User_E6ME3, The time-based rules/charges and approved time entries don't have a GL Impact. They will have a GL Impact if you have the Job Costing enabled and post the "Time Cost" Journal Entries.

@Ben Belzer, NetSuite Duplicate Detection doesn't have exclusion criteria based on the Customer Parent/Child relationship. When you set the detection based on "domain", it applies to all customers.

Hey @Ben Belzer, You can create a Scheduled Mass Update for the required customers to auto-mark their duplicates as "Not a Duplicate":

Hey @User_RLV0D, I see the status is queued for 9824 items. Is it still showing the same number? Some duplicate resolutions take relatively long to process. You may also have various tasks running in the background, which is why many of the items were queued. When you mention you can't cancel them, are you clicking…

Hey @User_9AUJK, I have built various scripts with my team to update Revenue Arrangements in bulk. Each use case may require a different script. Let me know if you would like to discuss this over a phone call.

Hey @Jeroen Sprangers ZS, We can build an integration to show the updated vendor catalog in your NetSuite instance. The integration can also built to generate a PO in NetSuite when the PO is created on the Vendor website. It might also be possible to generate a Vendor PO based on a PO created in NetSuite (provided we have…

Hey @Eva H, Yes, you can do that. SuiteSuccess isn't a specific database type. It is a selection of settings, reports, fields, and other custom objects deployed via industry-specific SuiteSuccess Bundles. Some customers don't use the "SuiteSuccess" bundles and work with consultants to configure their NetSuite account to…

Hey @Elina Kourouzidou, Did you select the "Account (line)" under the "Transaction Columns"'s Source List?

Hey @jmack_admin, You have two options: Credit the Invoice, then delete the Item Fulfillment and close the Sales Order. Once done, create a new Sales Order with the correct customer. Delete the invoice, Item Fulfillment, and Sales Order. Then, create a Sales Order with the correct customer.

Hey @Andy Galuski, The Saved Search you are trying to edit came from a Bundle and was locked. Now that Bundle's source account is inactive, you can't get rid of this Saved Search yourself. You would need to open a Support Case with NetSuite and ask them to help with this issue.

@User_7NEDX, You must map the "Business Unit" from the source transaction (e.g., Sales Order) to the Revenue Arrangement. Once done, the related Business Unit will be present every time the system creates the Revenue Arrangement. With the Business Unit present on the Revenue Arrangement line, you won't have errors when…

Feel free to open a case with Support and ask them to investigate. They have access to a copy of your account and can find out the cause. I will be surprised if it is a bug.

Perhaps the original JE was applied when you tried to change the customer, and the new one is unapplied.

Without access to your account, I cannot know what customization is locking that field. It might be a custom workflow if you are confident it is not a script. Also, there is a small chance that the native "Name" field is hidden, and a custom "Name" field is shown with a field display type set to "Disabled."

The "Name" field isn't locked natively when the Journal is editable. One of the scripts deployed on the Journal record is locking it. You can check the technical documentation of each script to see which one is locking that field and under what conditions. Most probably, they have a good reason to lock it. If you are…

Via Customization -> Scripting -> Scripted Records -> Journal Entry -> View