Aaron
09/02/2024, 10:53 AMCeligo AI
09/02/2024, 10:53 AMAI generated answer (using internal Slack threads):The best way to check for gaps in transaction numbering sequences in NetSuite is to create a saved search. This will allow you to identify where the numbering sequence was disrupted. Here are the steps to do so: 1. Navigate to Reports > Saved Searches > All Saved Searches > New. 2. Select the type of transaction you want to check. 3. On the Criteria subtab, add a filter for 'Main Line' is true. This will ensure you're only looking at the main line of the transaction, not each individual line item. 4. On the Results subtab, add the fields 'Document Number', 'Date', 'Name', and any other fields that might be relevant to your search. 5. On the Available Filters subtab, add 'Document Number' as a filter. This will allow you to search for specific document numbers in the future. 6. Save and run the search. This will give you a list of all transactions of the selected type, sorted by document number. You can then manually scan through this list to identify any gaps in the numbering sequence. If you notice that the numbering sequence has suddenly increased by a large number, this could be due to someone manually entering a higher number for a transaction. In this case, you would need to manually adjust the numbers of all subsequent transactions to correct the sequence. If you're experiencing issues with duplicate or blank transaction numbers when creating transactions via a script, it could be due to the 'Allow Override' setting being enabled. This setting allows for duplicate transaction numbers and generates the transaction ID during record initialization, rather than during submission. If you're not setting the transaction ID in your script, you could use the 'Generate Document Number on Save' field to ensure unique transaction numbers are generated upon saving the record. Please note that these methods require a good understanding of how NetSuite works and should be performed by a NetSuite administrator or someone with similar knowledge and permissions. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Celigo AI
09/02/2024, 10:53 AMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.811556
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.801303
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.795535564
Celigo AI
09/02/2024, 10:53 AM