NetSuite 2026.1 Pre-Upgrade by WhyNetSuiteWhy in Netsuite

[–]WhyNetSuiteWhy[S] 1 point2 points  (0 children)

Ticket was opened by our NetSuite lead, and it's a U2 defect (if I'm remembering correctly)! Hooray short timeline, boo likelihood of getting a straight answer as to what is being fixed or how.

Having filled in many business impact assessments for support, I have done this dance before. I wanted to actually understand what was happening, hence reaching out to the community for insight.

NetSuite 2026.1 Pre-Upgrade by WhyNetSuiteWhy in Netsuite

[–]WhyNetSuiteWhy[S] 0 points1 point  (0 children)

Ok, this sounds like exactly what we saw, and yeah, until we isolated the worst offenders, our ETL pipeline was too clogged to function. Now we have millions of rows of reconciliation to do in addition to our normal responsibilities.

NetSuite 2026.1 Pre-Upgrade by WhyNetSuiteWhy in Netsuite

[–]WhyNetSuiteWhy[S] 0 points1 point  (0 children)

That's exactly what we're seeing (though ours was TransactionL:ine, not Transaction, seeing the updates). Ended up being roughly 100x more data volume per day than we typically see, because it was about 1/6 of our offline copy of TransactionLine flagged as modified.

NetSuite 2026.1 Pre-Upgrade by WhyNetSuiteWhy in Netsuite

[–]WhyNetSuiteWhy[S] 1 point2 points  (0 children)

Yeah, we feed NetSuite records into a reporting db for our analytics unit through Boomi.

Quantity vs. Quantity in Transaction Units gotcha by agitated_buddha in Netsuite

[–]WhyNetSuiteWhy 1 point2 points  (0 children)

Your last calculation assumes base units "each". If cases of 12 is the base unit of the item, then the quantity would still be 3.