Has anyone else run into issues with the NetSuite2.com data source seeming to be incomplete? In just a few weeks, we've identified 3 defects - Customer.IsTaxable doesn't exist, Customer access role does not exist, and CustomerSegment.customergroup had the wrong data (the Id's were the same as CustomerSegment.id, not the customergroup ids as expected). This seems like this data source is in Beta or we're one of the first ones to use it, but our ACS reps keep assuring us we should use it over NS.com and that NS2.com has been in production for a couple years. So frustrated.

Yes, this has been discussed. I’ve mentioned a few times recently that it seems like they’re trying to push this messy and incomplete DB schema and acting like it’s so much better than the old one. There must be some technical debt that they are trying to get rid of on the NETSUITE.COM datasource. I’m continuing to communicate to our account rep.

We've definitely noticed missing columns and even entire record types not available in the new schema. I feel like it has enough data for about 80% of of our reporting and data needs, but there are quite a few things we cannot switch over yet. One big issue for us is that if you add a custom field of type Document, it is not exposed through NetSuite2.com, even though Netsuite.com makes the field available.

... and dont forget about primary key columns with nulls. We know these are 'views' rather than actual tables but still.

have any of you submitted support tickets for these specific issues - what kind of response was there? Of the 3 I mentioned, they confirmed 2 are "defects" (one they resolved, the other was just confirmed yesterday so is ongoing). But the other one (missing customer access role field) they claim would be an "enhancement", despite it being in NS.com and a core customer field.

re one of your issues, the 'taxable' field is available via suitescript ...

that's the one they just confirmed yesterday as a defect.