Connector Improvement: Netsuite 2 Lookup Tables Should Not be Non-Incremental
Reviewing the schema, it seems that Netsuite2 lookup tables are noted as non-incrmental. However, many of these are critical when trying to use other tables, such as transaction_line.
For example, for fulfillments, transactionLine has a "trackingnumberlist" field. This is a key to other lookup tables that provide the actual tracking number for a shipped order, "TrackingNumber" and "TrackingNumberMap." Each is over 303k rows in our Netsuite2 database as of now..
These are noted as non-incremental and when trying to include them in our schema, I'm warned about the spike in MAR that will result.
Transaction status is another good example of critical information related to our transactions, that is held in a non-incremental table
We need a way to bring in these critical tables without incurring a MAR penalty.
I should also note that working with Netsuite directly, there are built in functions, BUILTIN.DF([.....]) that bring in the data from lookup tables, without any additional joins. Perhaps additional columns can be added to the tables to bring in the results of the BUILTIN.DF functions along with the standard columns?
Happy to discuss further on a call with Erin as this is becoming a bigger and bigger problem for us.
-
Official comment
Hi Mike - for the supportcase table, is there a lastModified timestamp or is this table additive only meaning no updates can occur to a record once created? For a table called supportcase i find that hard to believe but please let me know if i'm wrong.
The reason that tables are reimport is if there is not a lastModified or lastUpdated incremental date field. The fact that a table just has a PK is not enough to make it incremental.
-
Another example is the supportcase table. It is marked as non-incremental and has a primary key? We need it sync'd at least once a day. Once a week on the weekend is not usable.
Please sign in to leave a comment.
Comments
2 comments