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

Community

Allow for syncing of NetSuite SuiteAnalytics Connect system tables

Answered
Gerald Williams User

Connector name: NetSuite SuiteAnalytics Connect

Table name: `oa_columns`, `oa_tables`, `oa_fkeys`, etc.

API documentation link: NetSuite Applications Suite - SuiteAnalytics Connect System Tables

Additional details: Having these metadata tables synced to our DB would be hugely beneficial for agentic (and human) modelling workflows which rely on understanding the source data from NetSuite, which can be quite cryptic at times.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Frank Fivetranner

    Hi Gerald,



    This request to sync NetSuite SuiteAnalytics Connect system tables such as oa_columns, oa_tables, and oa_fkeys has been added to our feature improvements backlog. Exposing these metadata tables could enable advanced modeling workflows and provide more transparency into NetSuite's data structures.



    To help us better scope this request, could you share more about your specific use case, such as the types of workflows you are planning or the challenges you currently face accessing this metadata? Understanding these details will help us prioritize and design the most useful solution.



    We will keep this thread updated with any progress.



    Thanks,

    Frank

  • Gerald Williams User

    Thanks Frank. 

    One challenge we have with NetSuite is that it is not always easy to infer what is represented by the table and column names, especially for our custom records.

    Enabling a human or agent to run queries such as the following would greatly improve our data modelling experience, as we wouldn't need to manually go into the NetSuite UI to see what the display name is of a field (for example).

    -- note that `remarks` is the display name of the column
    -- this is often useful for determining business context
    select
      table_name,
      column_name, 
      remarks 
    from oa_columns
    where table_name = 'customrecord_abc'

    Another benefit of having `oa_fkeys` available would be that we (or AI agents) would be able to easily confirm the actual join relationships between tables without having to make assumptions or go inspect the NetSuite UI. 

    Apart from these examples, I'm sure I don't have to explain the benefit of having source data metadata easily available for data modelling workflows.

    Let me know if you have any specific questions.

    Sincerely,

    Gerald