Sweet. I was hoping you would post back with it working. This turned out to be a nice learning experience.

Thanks Julie. That gave me the clues I needed to get what I was after. Here is the final version of my formula: Formula (percent) > Average > round(sum({transaction.amount})/nullif(max({estcost}), 0), 3) I realized after I got it working that the equation I posted above was reversed, but this gives us a project percentage…

Come on, all you formula nerds. Tell me I'm doing it wrong.

No, I only put Max in there because it needs a summary type of something; I tried them all. What I really need to do is divide a number on the project main record by a sum of numbers from the child transactions. X = {estcost}/sum({transaction.amount}) But that didn't work either. I have a feeling what I want to do is…

It turns out that I needed to, on the group record, to have an email alias (Exchange) to get emails to the group. In case someone is looking for an answer.

I have found that leaving the When Old Value is blank will allow this to trigger when that value is anything and only check for it going to whatever you have set in the When New Value is. I would imagine the reverse is true. You could probably be able to leave the new value blank as well and the search would key off any…

I was also getting duplicate emails for a couple of SS that have Created/Updated fields. However, I dug a little deeper and I think it was caused by a Workflow that was also trying to run in AfterSubmit. I changed it to Before Record Submit and I think my problem has gone away. If that is not the case, you have verified…

That's not a bad idea, actually. I'll keep that in mind.

This is becoming more and more of a problem at my company. More and more people are complaining of it. It seems to have gotten worse lately.

Funny that you reply to this now. I had forgotten all about it and even ran into it again the other day. I was getting two emails for a set of alerts I had built. It turns out that others are not getting the dupe emails but I had totally forgotten about this. It only happens to me it seems so it's not a big deal. Does this…

AHHHHHAAHHHAHHH Corey! Job security in the digital age. Anyway, so trigger types on WF's and suitescripts affect SS email sends when records are created/updated? What's next, the moon's phase affects the rise of my souffle? No really, I don't get the correlation. Ok so if I can remember correctly, this double send has to…

How can I fix it?

No, it only sends one. Interesting.

Actually the above formula gives an answer but it is wrong. I worked with NS support for a few weeks on this and we have come up with: (cast({custevent_cxs_init_res_time} as date) - {startdate}) * 1440 This will work for a great majority of the results. There is a defect with the custom date/time fields and their use,…

Who really knows, but it diminishes my statue as NS Guru in the office-see. in the land of the blind, the one-eyed man is king This is how I stay ahead of the curve. Well that and by creating absurdly obscure and complicated automated processes that if fired I would have to be kept on in a consulting basis just to keep…

FYI, I finally came back to this formula and this works: round((to_date({custevent_cxs_init_res_time})-to_date({date}))*1440)

The alert I was talking about does key off when a certain field is updated. saved search alerts that are checking against updated fields

Ok, update. It turns out that, in my user event script, I am using the after submit event and since I submit the record it is saving the record again which triggers the email alert a second time. I was able to change the logic to before submit, but that limits what I can do from here on out. If I want to be able to have…

I opened a new ticket today. Thanks.

I do have an after submit script that gets the value of the assigned to field and sets another one. But, I would have thought that the updated fields would have caught that as first it is only getting set once. I guess I have to open a ticket.

Does the search return dupes when the script has been disabled? Thanks, DO you know how to fix this Robert?

Sigh, turns out I can do what I wanted by using the Criteria: Assigned = TheGroup (or) employee.group = TheGroup Anyone see a flaw in that?

I was a little unclear in the code pastes above. {date} and {createdate} work the same in this formula (I tried both, and I believe they are both date/time - one is listed as create date and one as incident date). The difference I wanted to point out above was between {activity.createdate} and my custom date/time field.…

Why is this still not exposed? Also, using job (project in our case) as a criteria doesn't seem to be respected. For instance, I have a transaction search: FILTER DESCRIPTION FORMULA Statusis Invoice:Open Main Lineis true Memorizedis false Formula (Text)is not empty{job.entityid}Prepaid Processed (Custom)is false Typeis…

I was just looking this up yesterday. From the help at: Marketing, Sales Force Automation, and Partners : Sales Force Automation : Sales Forecasting : Setting Up Sales Forecasting The Calculated Forecast NetSuite calculates your sales forecast as the sum of the following: Opportunities with no estimates attached or with…

Thanks for the answer. I had actually figured it out and was going to post back here this morning, but you beat me to it. I used the exact same approach. Nice to know I did it right? Thanks

Splitting the string is a good idea, I will try it if I run across this again. For now, I just hacked it with the like statement. It was only a one off search, anyway. Thanks for getting an answer to this. I was going crazy for a minute :)

FloDocs!! Check them out! Seconded. I just checked out their booth today. Super impressive and really just the thing we need.

Any resolution on this? I am sending PDF's by email to many customers and all are receiving the wrong date.

/hangshead I just found that in the SuiteAnswers directly after I posted here. I guess I should reverse my procedure :) Thanks