Thanks for the update, rnedelkow! I'm no longer seeing errors. Is there a reason why these kinds of issues don't show up on the status page (status.netsuite.com)? Wouldn't this be a SuiteAnalytics Connect service disruption? I always check the status page first whenever I have frequent ODBC connection errors, but there's…

I'm having the same trouble. Seems to be working sporadically.

As a followup, I just finished a perfected search (using regular expressions) for Customer IDs that don't fit our company's numbering scheme. Our numbering scheme is: For Parent Customers: 4-digit year, then 6-digit incremental number (e.g. 2008123456) For Sub Customers: 4-digit year, 6-digit incremental number, colon,…

Awesome, thanks for the direction! I've got a decently-working search that will find Customer IDs longer than 10 digits (I'll work on a search for non-numeric values later). For now, I've got the following criteria: Filter: Formula (Numeric) Description: is greater than 10 Formula:…

Okay, thanks for letting me know!

Thanks, Yang. We may end up taking an entirely different approach to stopping previous customers from re-registering (creating duplicates in our system). But if we come back to this, I'll post my solution.

Thanks for your reply, Steph! That was my backup plan in case we couldn't put the Lead Source on checkout. Thanks for the details.

Thanks, John! I didn't realize you could use login for users that just have the customer center role. I got some Ruby code working to test this concept: module NetsuiteHelper require 'rubygems' gem 'soap4r' require 'defaultDriver' class Soap def self.test_login(email, password) driver = NetSuitePortType.new…

John, I think what you suggest is exactly what I need to do in my situation. I'm planning a separate site that will use customer records (pulled out via odbc) as the users and am hoping to find a way to authenticate them through NetSuite (using their existing NS passwords) via web services. If the response is success, it…

I started getting this same error again last night around 2:40am ET. Anyone else getting this? ODBC::Error: HY000 (10169) [unixODBC][NetSuite][ODBC 64 bit driver][OpenAccess SDK SQL Engine]Error getting the literal value of right operand.[10169]

I was having problems between 10 and 11am ET, then one error around 2pm ET, but haven't had any errors since.

For posterity, I found a new SuiteAnswer (Answer Id: 69493) that addresses this issue with a fix: https://netsuite.custhelp.com/app/answers/detail/a_id/69493/kw/right%20operand To eliminate the "Error getting literal value of right operand", use to_date(date, format) SQL function to properly convert date columns. I updated…

I had sporadic errors March 10-12, but I haven't had any more since then. I didn't make any changes, they just stopped.

Hey, thanks! I haven't had any errors for the past several hours. I'll give that a shot if it continues to be a problem.

Yeah, I started having issues again from 6:30pm ET and on to this morning.

After several months of no problems, I'm getting this same problem again today. This SQL: SELECT CUSTOMER_ID FROM customers WHERE last_modified_date > '2015-08-04 20:41:29'; Produces this error: ERROR -- : HY000 (10169) [unixODBC][DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Error getting the…

I've been very happy with it. It's been fast enough for what we need. Every half hour I pull down any records that have changed on a few important tables (like CUSTOMERS). Then nightly, I pull down any records that have changed on the less important tables (like MESSAGES). That gives me a fairly up-to-date copy of almost…

Yeah, I do. I query TRANSACTIONS and TRANSACTION_LINES separately. Up until yesterday, I'd never seen duplicate records (all columns in the rows were exactly the same). The only reason I noticed the problem was that my scripts failed because MySQL didn't like the fact that I was trying to insert multiple rows with the same…

Thanks, that just helped me out a bunch, too.

Yes, we're having trouble, too. I have 3 MSSQL DTS jobs that run overnight (between 4:30am and 8am EST) and they all failed. When I try to connect personally, I'm getting this error: [DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK Client]TCP/IP error, connection timed out

Thanks, will do.

I've got DTS packages in SQL Server that connect via the ODBC read access to NetSuite, run SQL queries and pull the data into SQL Server tables. Today, when I went to run the packages, I get an error saying the DTS can't run. So I go in to edit the DTS package and check the connection properties for one of the NS…

Yep, we're getting the same thing when trying to connect through SQL Server.

Yes, we're getting that error as well.

I take that back. I got that error when trying to use the test VISA CC number. When I used a valid MC number, my test order processed successfully. But our weekend orders were abnormally low, so we're still investigating, to see if something went wrong.

Down in NC

Thanks, Sean! Yeah, I was considering the scheduled workflow. My biggest issue was the time delay. A "notified" flag on the case is a good idea, too.

Here are the notes I took on my final process, if this helps: I created a new Workflow for Case records, setting the following: - Event Based - On Create - Trigger Type: After Record Submit - Event Type: Create - Context: User Event Script - Condition: Case Origin = E-mail I created a single State (default settings) I…

One other note, for posterity...if you want your workflow only initiated by inbound case emails, use these settings: Trigger On: After Record Submit Event Type: Create Context: User Event Script

Okay, after banging my head on this since yesterday, I've discovered some things. Yes, you can initiate a workflow on the creation of a case record from an inbound case email. However, as far as I can tell, the workflow is initiated prior to running through the case territory assignment process. I created an action to send…