I believe what's happening is this: if the join doesn't exist, then the results can act like a filter. For example, you have a simple search for all items, and you get 100 results. Only 10 of these have ever been sold, 2 times each. If you add a result column of transaction.amount, you will get 20 lines in the results.

Here's the script... it should be rewritten to clean up the date function and use parameters, but it is working. There are also custom fields in the script that you will need to edit. function find_late_invoice(type) { //set minimum overdue days and increment of days between emails var min_days = 15; var increment_days =…

Yes it's possible, I run a very similar process with scripting.

I don't think you want anything but the img tag, get rid of the other lines. Also, try putting the html in the Introduction section. If that doesn't work, then try the Body section.

The way to do this is with a Saved Search (not a report), using summary criteria. Here's an example: Criteria Standard Type is Sales Order Main Line is false Criteria Summary Sum Formula (Numeric) is 0 case when {item} = 'your item number' then 1 else 0 end Results Document Number Group

A better way to do this is to use Campaigns. If you have time to switch the process, this would work well for you. If you need to stick to Saved Search: [LIST] [*]If it's the same image to all recipients, you can just hard code it into the Email section of the saved search. [*]If each customer gets a different image, then…

Edit your Saved Search, in the 'Email' tab, choose the 'Customize Message' subtab. Place the image url (with proper html) in the 'Introduction" or Body fields.

The code you have won't be accurate if you don't fulfill on the last day of the month. Instead, you could hard code it with CASE statement. For non-leap years: CASE TO_NUMBER(TO_CHAR({systemnotes.date},'MM')) WHEN 2 THEN 28 WHEN 4 OR 6 OR 9 OR 11 THEN 30 ELSE 31 END If you want to include leap year logic, nest another CASE…

Searching for 'non-existing related records' is difficult in NS. I would suggest creating a Customer summary saved search like this: [INDENT]Standard Criteria Transaction:Type is 'Invoice' Summary Criteria Maximum of Transaction: Date 'before' 'start of last month' Results Customer (group) Transaction: Date…

Open a case with support. This has happened to me before and took some time to resolve.

"Average Days Between the Purchase" could be calculated using a summary search, as long as you use a defined time period. For example if you limit your search to the last 365 days, then your average days is 365/(number of orders), or alternately 365/(number of orders - 1). You'll have to make it a Summary Search with Count…

There might be a way to find the date of first purchased using SQL statements, and use that in your formula. But I would do it another way: create a custom date field on the item record called 'First Purchase'. Do a CSV import to initialize this field for existing records, and going forward have a script/workflow populate…

If you create a saved search, you can Summarize by Grouping the Support Case.

Use a formula(text) field

Sounds like it should work, please post your results if you test it.

This is how I would do it: 1. create a custom field called 'Sales Amount' on Customer records 2. create a scheduled script/workflow that places the value in that field, based on your saved search 3. now you can create another saved search that shows the value of this custom field.

You're not going to return any Leads from this search, because this criteria line is never true for Leads: Transaction: Type is any of Credit Memo, invoice, cash sale And this one may not be true for some Leads Transaction: Main Line is true

Here's the best way to do it: create a custom field called 'Search Description'. Make sure that this custom field is included in Global Search. Then create a user event script that synchronizes the normal description field with the custom field. Here's the chunk of script I use: function update_descriptions(){ var…

Just an idea - not sure if it would work... add a custom Transaction Column Field, uncheck the 'Store Value' field, make it a formula with value of {amountpaid} or whatever field you need.

You could eliminate that by changing the formula to Case When bin = primary then case when stock <= 15 then 1000 else 0 end Else case when stock > 0 then 1 else 0 end End Then make summary criteria for this formula summed >= 1001 As long as you don't have 1000 secondary bins

I would do it as a summary search with case statements. In pseudo code: Case When bin = primary then case when stock <= 15 then 1 else 0 end Else case when stock > 0 then 1 else 0 end End Then make summary criteria for this formula summed >= 2

Member item:location isn't the same as Member item:inventory location Is that field available?

Here's what I do: make a custom field called 'Search Description', check the box for global search, and apply it to your items. Then add a user event script that syncs the custom 'Search Description' field to you standard description field. See here: https://usergroup.netsuite.com/users/showthread.php?t=28227

Here's a snippet from a working script of mine. Results from a summary saved search with a formula(text) column. function main_function(type) { ... var so_search = nlapiLoadSearch('salesorder', 'customsearch602'); var so_search_results = so_search.runSearch(); so_search_results.forEachResult(get_so); ... } function…

How about a saved search that sums the usage, then the saved search to the Item form. I've got a similar search for 'Where Used' on the Item record.

I run into this too, and since it's from a locked bundle, I can't change the script behavior. One workaround is to define your saved search with 'Updated Fields' Add fields to send update alerts only when the selected fields' values change. Enter old and/or new values to send alerts only for updated records with these…

I have a few saved searches that do this too, in my account I suspect it's from a bundle where a user event is updating a field aftersubmit. Check the system notes on the case record and see if there is a field that gets updated via script.

Here's one way: 1. create a custom field (integer) on the record. Hide the field or bury it on a tab somewhere 2. with a beforesubmit user event, add 1 to the custom field value if the case status is the one you want. You could probably do this with a workflow too 3. Run your saved search for custom field value = 1

John - I ran into this same problem so I created an invoice with all my items on it, with a qty of 0, rate of 0.00, etc. Then all the items show up on transaction reports... was an ugly hack but it worked.

try this instead case when {custbody_date} IS NULL then 0 else 1 end And if that doesn't work then debug it by making the formula result equal to {custbody_date} and see what the results show