I didn't receive such an email. The site doesn't appear to allow me to register for sessions, either.

Thanks, Robert!

Mine is wrong. I'm Central Time and have it set to auto-detect daylight savings. I posted at 4:24 but the timestamp on my post shows as 3:24. Well, this post shows 3:31 but it's 4:31 here.

I just fixed it by changing my Auto-detect DST to Always On, saving, then changing to automatic. Seems to be fine now.

Nobody knows?

I'll just say I concur, and I think it's a short-sighted method(?). Well, I'll also say that I've offered very specific, constructive advice to the reps themselves, managers, and a VP or two. I am frank in my CSAT responses and often get a followup from a manager about the way a case was handled.

Interesting. I thought that was the native serial number field. I don't know what you mean by "it is showing as a box." Perhaps a screenshot of that would help. What type of field is it? I don't use inventory so it's a bit hard for me to conduct a quick test. Quick guess with what I know now is you might reference it with…

Sorry, I don't know how much help I can be since I don't think in my dev environments I can even enable the feature that allows that. However, I can see why it might behave that way. How is the system to know which field in your inventory detail it should include? Serial, expiration, available, qty? Perhaps another…

To be clear, are you using the ${} notation such that it would be ${record.promocode}? I did that and it works. If so, ensure your formatting is such that it will be displayed how and where you expect it, perhaps by simply copying another line.

Which fields is your new custom field? My guess is Discount Reason, but then I'm unclear on the point of your second screenshot. Whatever it is, you can get the id of the field then code it into the template using another field as reference. Like if you see {item.quantity} in the code and your custom field is Discount…

Someone in NetSuite Professional Services did this for us. Works well. I'll admit that I don't quite understand how it works. Funny though that it actually didn't work quite right and I figured it out enough to improve it. Wish I had time to share but not right now

Bump. I'm interested in this, too, but mostly for a faux package presentation. My current vision is I'd have a custom column on an invoice to indicate the package to which a set of items belong (e.g. 1, 2, etc). No matter where in the invoice the line items are (i.e. one line could be in row 2 and another in row 8), the…

Big Faceless Organization. Basically it helps you make charts, graphs, PDFs. You can read some about it here - http://bfo.com/

I want to agree with skenyon. I thought I read that in SuiteAnswers or some documentation but can't find it now. Try it out and report back!

I don't actually know the answer. Even if I thought they'd be fine, I advise you if at all plausible to process all the existing bills and not enter any new ones before making the workflow changes. If some bills are problematic (would be in the middle of process for too long), consider killing them entirely.

I remember dealing with something similar a few years back. There is a way to get the actual logged in user's email address, I think. I vaguely recall having to use SuiteScript and nlapiGetContext. It may have been nlapiGetContext().getContact() or nlapiGetContext().getEmail(). Unfortunately, I don't have access to that…

Jason, you said you're using the Administrator role. Have you actually tested while using the Swyft_Sales Administrator role? According to your condition, this shouldn't lock while using the Administrator role. Also, turn on logging and see what it turns up.

Thanks for the suggestion, but it would be easier to just use script. Workflows are another example of NetSuite releasing something and then doing nothing at all to improve it over time. :( I don't agree with "nothing at all." They've made some good strides with it. I think it's foundationally challenged. I've felt for…

I have not been able to get Workflows to fire on EXTERNAL forms. I've only tried it for the external case form. The reason I was doing it was to satisfy a requirement I didn't agree with, so I presented the challenge with strong advice to change our business process. That advice was taken. However, to satisfy my own…

Thanks, David. I think you understand my request, but I think an example will ensure you (and others) get it. Excerpt of a workflow might look like: Before Record Submit: -- Set Field Value: Employee = Current User w/ condition: Type: Create I'd like to see the code this generated that might look like: function…

Yes and yes. 1. There is a caveat to the 'yes.' The supervisor (or next approver) should be able to approve things "below" them - natively to NS, that is. I'm not totally sure of specifics, but I think you would have to make your own notion of "approver" or "next approver" to set that next person to after a period of time.…

Thanks for the response. Is the condition of total=0 on the Workflow definition or on the action. Currently I have it on both and still not working. Just on the action. My workflow is a form control I want to initiate on all new and existing records. Additionally, I have one state and it never exits.

Try using the "Show Message" action triggered on Before User Submit with condition Total = 0. I tried it successfully in my existing form control workflow that initiates On Create and On Update with All Trigger Types in Context User Interface. I tried a few tests with Field Change and Field Sourcing but those weren't…

Perhaps the workflow is expecting a transition from Open to Closed, and it doesn't get that when an opp is created in the Closed status. Does the opp show up in your saved search?

Nevermind. I used that formula but forgot which environment I was working in. Found the trigger wasn't set to create in this environment. That one works. I'm not pleased I have to use so many API calls for it to work and the method I described in my initial post doesn't work. Bottom line: I can get to the value I need so…

To retrieve value from a desired field use function nlapiGetFieldValue(). Hope this is what you are looking for. Thanks. I've tried something like that, but haven't gotten it to work either. Maybe my syntax is wrong or something. nlapiDateToString (nlapiAddDays (new Date(), nlapiLookupField ('customrecord218',…

Isn't there already a "last modified" field on every record? I may be misunderstanding your question or need, but are you actually trying to create a new field every time a record is edited? Or just create the field the first time the record is modified then update that field with the timestamp of the last modification? Or…

I bet it's the Store Result In field :o

I'm trying to use the Visual Builder to set the User Role condition, but there aren't any values in the Field column/field. It's just blank. But that field is required. I've never tried to restrict a workflow action (in this case a button) to a role. How would I do that? Sounds like you selected User Role in the Record…

It is actually going out tonight. Correction: Next Tuesday. Interesting. May I ask why Tuesday? Are the updates switching from Thursday evenings?