We are also experiencing significant server delays for searches yesterday/today.

The Commission Overview report is now screwed up as well... this was the only commission report that accurately reported numbers... but within the last week or so this broke too. We can no longer use the commission module since we don't have any report that has accurate data. Is anyone else using the commission module and…

I have both the header and line level location setup. The setting that won't save is the location at the line item level for the invoice or fulfillment record. Whenever I save those values return to null.

I agree... I've had a couple phone calls and quick case resolution in the past week. Great job!

I have 3 companies where the out-of-stock messages are not working now... the messages were working fine a couple days ago. This has to be a NS system wide problem. Is this an identified problem being resolved or is it still unknown?

6/17/2008 11:59 PM Eastern 6/17/2008 9:09 PM Eastern 6/11/2008 2:35 PM Eastern Additional details from one failure below: Reporting-MTA: dns; appmx1.netsuite.com X-Postfix-Queue-ID: 547F25D045F X-Postfix-Sender: rfc822; derek@xxxxx.com Arrival-Date: Wed, 11 Jun 2008 11:35:54 -0700 (PDT) Final-Recipient: rfc822;…

Thanks... I did do this as a work around. However, I'm concerned that the standard NS version allows non-admins to hand out any role. From my support case filed it appears NS is working to restrict this from their standard out-of-the-box version. I'll keep you updated.

For anybody following this post, I found one way to eliminate the items from appearing in the KB search. If you put the item on "special" it will not appear... this works for us since we don't use the website functions of NS.

Using your second method, go to the 3rd tab (Attachments), check off "Include Transaction" and select Type (such as PDF) That will send the Invoice (or Sales Order, Purchase Order... whatever transaction you are viewing) to the email recipients.

What function does the current "Send E-mail" checkbox serve? I can't find anything in the help docs.

We've always had good luck... the only thing I wish was faster was the 3-4 business days to settle as opposed to a 1-2 day timeframe normally associated with ACH. In any case, we really like the convenience and haven't had any problems.

You can create "custom records" (essentially create a new database) to track these fields. The custom records can be associated/related to the customer/contact/sales order, etc. so it makes it easy to reference these files. Custom records are also accessible via searches so you can create extensive reports/KPI's/alerts,…

In your Transaction search criteria, set the field "Main Line" to "Yes"... this will return just one line per transaction (as opposed to one line for every line item of every transaction). If you also want to get rid of duplicate Customers (in other words, just list the Company name once instead of once for every…

Thanks! This is helpful.

I'm still unable to do this (create Project Task from Job Record). Has this field been exposed or am I missing something else? Thanks

I was able to workaround this issue by initating the Workflow to be a "Scheduled" based initiation -- and created a saved search which mirrors my selection process. The "scheduled" initiation is automatically processed every 30 minutes and anything found in the saved search results will be initiated into the Workflow…

File case #1207404

For anybody interested in this topic, I've actually simplified the entire workflow to two States -- the "send email" State and the "exit" State. In the send email State the action tab includes every type of email we would send under this nurture campaign -- all scheduled/filtered against saved searches that run against…

Last night I tried my workflow as defined above (with "central routing") and it didn't work but for an odd reason. The first State is simply: Action: Send Email, Scheduled, 1 hr Delay, 0 recur Transition: Delay 3 hours then move to State 2 (The central routing logic doesn't kick in until State 3 & 4) The result is the…

Additional tests on other workflows confirm that if I use a time delay or recurrence of "hours" it take about 4 hours to run the first time and runs approximately every 4 hours thereafter. I'm still assuming this has something to do with me being an East Coast timezone and the workflow deployments are on West Coast time.…

I will file a support case. I've been able to replicate this on several workflows. My guess/hunch is it is because I am in the Eastern time zone but the scheduled scripts for workflows are executing based on Pacific time zones. So... if I enter a State at 12:00 pm (Noon) Eastern with a 1 hr delay... it actually executes at…

Would this work? Setup a State which is basically a central transitional routing station... this State would include several transitions all set to a 1 day delay. Consequently, the values would be checked every day and when a match is found it performs the action and returns back to “central routing”. This looping…