October 17, 2024 at 2:14 pm
Hi we built a gateway from sql server to netsuite using an oracle competitor's odbc driver.
once it was standing we noticed 111 columns missing in the linked server views for i believe just "salesinvoiced", customers and items alone. we have nsaw but its on a different netsuite instance and i believe out of scope of this question. as far as i know most or all of the missing columns are standard not custom and i can query them on netsuite using suite ql. according to the very first rep we spoke to at oracle, if you can query a field in suite ql on netsuite, you can get it thru an odbc driver.
I've heard a few things thus far that dont add up so im asking the community if the've had a similar experience..
one thing that strikes me is that #3 may be illegal (monopoly kind of thing) if it actually blocks (indirectly) the competitor products from seeing a huge percentage of fields.
October 18, 2024 at 3:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
November 13, 2024 at 7:18 pm
This was removed by the editor as SPAM
November 14, 2024 at 9:20 pm
i think somewhat consistent comments are starting to come in from CData (the competitor) and Oracle Netsuite.
CData clarified that their odbc driver taps into netsuite's suite ql API. and there are restrictions on what will show based on a sampling they take of i think the 1st 1000 rows. i believe (dont quote me) if all 1000 have a null in a specific column, it is discarded but i believe there is a way to sample more. ive sent them a question asking "if we start using such columns or introduce non null custom columns will they automatically show without a re install". and we did introduce one non null value into a customer column previously missing from cdata's driver. its currently on one customer only. we'll see if it spontaneously shows up in the odbc world.
netsuite echoed the latter about the API labeling the api as REST too and shared additional links specific to CData on this subject.
im starting to think there really arent views per se in netsuite and its still unclear what NetSuite2.com is. i'm starting to think that oauth2 and other security approaches arent the culprits here in hiding fields. there is more to learn. i am concerned that if we run some kind of conversion on netsuite where all values of a given column are temporarily nulled, that our etl will abort as it references columns that at that time wont be returned. this feels somewhat messy.
November 15, 2024 at 2:13 pm
i can confirm today that CData's odbc driver does indeed show previously hidden netsuite fields once they start getting used (ie arent all null).
There is what sounds like a choice that is dependent on whether "metadata caching" is turned on (which im getting clarification on) and then 1) a 2hr interval during which no connections have been made to netsuite, or 2) issuing a reset schema cache call.
Im not sure and am checking but suspect restarting their service would update the metadata as well.
I'm told this will happen for newly added / used custom fields as well.
I believe for any field, roles could impact whether a column shows anyway.
November 17, 2024 at 3:04 am
This was removed by the editor as SPAM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply