Has anyone lost their access to the <NetSuite.com>...
# suiteanalytics
s
Has anyone lost their access to the NetSuite.com schema (Connect schema) after a recent NetSuite renewal? Our NetSuite service renewed over the weekend, and when it did, we now get this message:
The <http://NetSuite.com|NetSuite.com> data source is no longer being updated and is not an option. Use <http://NetSuite2.com|NetSuite2.com> instead.
j
they announced they were closing it for any accounts that hadn't previously used it. My understanding is any accounts that had used it previously should still have full access
s
Unfortunately, though we have used it every day for over seven years straight, they took it away from us. We are requesting to have it back, as we also believed we'd still have access, because of our prior usage of it.
j
oh crap. I need to check some stuff our end too
d
This is pretty worrying
s
The good news is that NS support restored our access ( a day later). The bad news is, we had to work with three different shifts/regions of NS support reps (APAC, EMEA, and AMER) for almost 24 hours to get our access restored, and it was a real struggle to convince them why we couldn't just convert all of our queries in production to the new schema very easily. However, my next task will be working on converting queries so this doesn't affect us again in the future.
The reason it happened is that someone at NetSuite "accidentally" removed our SAC module at the time of renewal, then re-added it a day later. But that made it look to NetSuite like we were a brand new SuiteAnalytics Connect user, so we were prevented form using the old schema. They probably had to backdate our module or set a flag or something on the back end to make us look old again.
Well, shoot, out of one problem into another. Apparently, they took away all of our SuiteCloud Plus license, even though we are paying for two of them. How hard is it to just renew service?
d
Converted some queries from v1 to v2 recently and v2 schema is an absolute mess compared to v1. Documentation is poor too, in some cases we had to look at actual data to find the correct tables\fields because the names are completely different. I think it will be a huge undertaking for some companies to migrate.
Also, one of my clients has had a case open for around 7 weeks now because we can't query 'transaction' or 'transactionLine' table in v2. How can they migrate queries if two critical tables are not even accessible!?
s
Yeah, I already pointed out to them a few of our queries, against transaction actually, we can't convert over because some of the columns are not available in the v2 schema. We had already begun looking into that months ago and determined it wasn't possible.
d
v2 is definitely still beta imo
This is one of the mappings between v1 and v2 which is absolutely comical ...
message has been deleted
What do you do if you have hundreds of queries with zero mapping documentation supplied by NS? The only way we managed it is literally digging around and comparing actual data. Its crazy.
s
Yeah, I wonder the same thing myself
j
And good luck if you have ARM because they removed the link type 'Revenue/Amortization Recognition' for some reason... 🙄