Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Netsuite2 nexttransactionlinelink Change to incremental

Paul Kanterman User

The nexttransactionlinelink table is currently defined as non-incremental sync.  However, it does have a last_modified_date column and key columns defined.

Queries against the table have shown that previousdoc/previousline/nextdoc/nextline when taken as a whole are unique throughout the table, and the NetSuite schema does identify the four as keys.

In the source NetSuite2 table, these four columns (as one surrogate key) are absolutely unique.  In the Fivetran imported table, they are also unique, except for the last_modified_date. 

It seems that if the four columns noted are treated as a surrogate key, this table would be a candidate to be converted to incremental refresh.  

I am happy to jump on a call to discuss.  I can also provide the queries I used to research the table.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Erin Fivetranner

    Hi Paul - 

    Thanks for submitting this request. I see your screenshot below, however for those two records both have the same values for the 4 fields you state are the primary key. Was this record deleted? I'm not sure if i understand the situation for these 2 records. At this time though, Netsuite doesn't denote a primary key or composite Primary Key for this table. 

    Best, 

    Erin

  • Paul Kanterman User

    That is kind of my point.  The last modified date is the only thing that changes.

    The point of the table, it to provide the relationship between documents, so we can link Sales Order Line with the subsequent, Invoice Lines, purchase order lines, etc.

    The only difference between the Fivetran version of this table, and my source Netsuite2 table was the additional lines for the last modified dates.  But again, even where that date changed, the underlying columns I highlighted did not.

    It seems ridiculous to have over 5mm columns each month in MAR, where the overwhelming majority of them have not changed.

    Happy to jump on a quick call to discuss.

  • Tim Nickason User

    Did this ever get resolved?    I've been looking at this as a candidate to replicate but without a primary key, I'm not keen to pay high MAR cost each month for it.