Hi,
I'd like to issue a warning for everyone that use saved search alerts on transaction item lines. (it might affect others)
we have been using a couple of saved searches which are set to send alerts when a particular header-field on an order goes from 'F' to 'T'. We have been using those searches successfully for at least 3 years.
As of middle of September some of them have stopped working without any error-notices or similar. The only way we noticed recently was from a comment from one of the usual recipients that they "missed the usual alerts".
After my debugging, I identified at least two things that ruins the alerts. (note: scheduled e-mails are fine)
Non-stored Formula Line Item Field
In one of the searches, the result includes a field that is non-stored and is defaulted to a formula. In this case nvl({value1},{value2}).
Both {value1} and {value2} are also non-stored formula line item fields.
If the search includes this field, it will not send out any alerts anymore.
If instead using a formula(text) set to the same formula nvl({value1},{value2}), the alerts will be generated, but that field will then show "ERROR: formula error". Using either {value1} or {value2} directly will also result in no alerts.
Join fields on Item
In another search that silently stopped working, we had included a criteria that was a stored field on an item.
If adding any joined fields in Item-fields... ,either as a criteria or result-column, the search will no longer generate alerts. I've tried both custom fields and standard fields on items, none of them work.
For example using the field Item is perfectly fine but using the field Item.name or Item.internalid will not work.
I've created a case for this with Netsuite support, 3270020, and I'm now, as usual with Netsuite Support, struggling with the rep to get him to understand that this has worked for several years and is not "Expected behaviour". For the moment he has directed me to an Enhancement Request that is at least 5 years old and doesn't really fit. Enhancement:159436.