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

Community

Connector Improvement: NetSuite Connector - using incremental on transaction_tracking_numbers and other similar tables

Answered
arshad jamal User

Hello Team,

We would like to get feature improvement to NetSuite connector. It seems like there are some tables which do full resync after every regular interval but some of those incremental tables can actually use last_modified_dates from their linked tables. We did speak to NetSuite support team and they said the same thing to connect to linked tables to get primary key or last_modified_dates. This is a very important fix as current logic spikes or MAR count.

Example: For transaction_tracking_numbers table below was the solution suggested by NetSuite support.

"The way we can get the primary key such as datemodified or lastmodified is to create a custom field for the related transaction record, and retrieve it through here. I have attached a sample code below. Kindly note that this is using the NetSuite2.com data source, and record/table names may differ from your current implementation.

SELECT 
    tn.id AS tracking_number_id,
    tn.trackingnumber,
    t.custbody_cust_datemodified
FROM 
    TrackingNumber tn
JOIN 
    LinkedTrackingNumberMap ltnm ON ltnm.trackingnumber = tn.id
JOIN 
    transaction t ON t.id = ltnm.transaction
WHERE
type = 'SalesOrd'

The query links tracking numbers to transactions, extracting tracking number details and their modification dates from Sales Orders."

 

Please sign in to leave a comment.

Comments

5 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Arshad, 

    Thank you for submitting this feature request. Unfortunately, we cannot support this type of operation as it would require an pre load transformation which is not currently supported by our connector. I would consider asking Netsuite to support the addition of a last modified timestamp instead where our connector would then automatically pick up the column and make the table incremental. 

    Thanks, 

    Frank

  • arshad jamal User

    Hello Frank,

    We have already spoken to NetSuite on adding the last modified timestamp and they cannot do that since it already exists on transaction record. Fetching last modified timestamp from transaction table seems very straight forward. In fact, lot of tables in NetSuite2 would be using similar approach. We would like to get NetSuite connector updated to handle this issue.

    Thanks,

    Arshad 

  • Frank Fivetranner

    Hi Arshad, 

    Can you confirm a couple details:

    • Is this for NS1 or NS2? 
    • Is this field custbody_cust_datemodified the correct field? I'm not seeing this field in our documentation which makes me think it's a custom field, but I'll let you confirm. 

    Frank

  • arshad jamal User
    • Edited

    Hello Frank,

    This request would be for NS2.

    It seems like the column name is different to what was provided by NetSuite support earlier.

    It's called lastmodifieddate in NS2. I can also connect you guys with NetSuite support if needed.

    Please find below sample code:

    SELECT tn.id AS tracking_number_id, tn.trackingnumber, t.lastmodifieddate

    FROM TrackingNumber tn

    JOIN LinkedTrackingNumberMap ltnm ON ltnm.trackingnumber = tn.id

    JOIN transaction t ON t.id = ltnm.transaction

    Thanks,

    Arshad

     

  • Frank Fivetranner

    Hi Arshad, 

    Thanks for providing this. What is the main use case for shifting these tables to incremental? We've made a couple changes that make reimport tables easier to work with. One is the release of 2025 updated pricing which means that unchanged rows in a reimport table are no longer charged. The other is the release of a "Re-sync reimport tables during every sync" feature which allows customers to control when reimports happen rather than using a given time interval. Hope these new features help. 

    Frank