what record type did you import the created by for?

bill payments

I have been in this situation, and NetSuite has behaved as by design, so support are correct in that there's nothing for them to really do. In our case we had ~15 million transactions to update, and knew in advance that this would happen, so we prepared a list in advance. It isn't going to be fun for you to clean up. You have a few options. 1) Write a map/reduce to re-apply. Determining the previous payment applications is not fun - have you got a relatively recently refreshed sandbox?. 2) Ask support to roll back your production account to Friday.

I do have the sandbox that was refreshed a month back but support is asking for $15,000 to do a data revert

How big is your business? Are we talking hundreds of records, tens of thousands?

I had something similar happen (with less records though) a few years back and NetSuite didn’t help AT ALL to fix it. I don’t understand how they can have records just unlink themselves for no reason, it’s completely unacceptable.

I was under wrong impression that data restore is part and parcel of the subscription, it turned out to be a myth. We are already very unhappy with how netsuite works, considering we were already considering moving to Oracle Cloud ERP, this will only push us away from netsuite further

This is a little scary! What exactly about the import caused the records to unlink? Guess I'd like to understand better when this will happen so we can avoid, or prepare.

for us, we were just setting the value of a custom field

It's more fun when it removes the customer/vendor name from a journal line

Is it specific to updating custom fields, or any updates? @CD how is it behaving by design? Sorry - y'all got me super concerned now!! Let's say I were to update the invoice date on several invoices that have already been paid via import- is this going to clear the linked payments?

lol

They closed my most recent bug - which is an API function that is supposed to return an integer, but in fact returns a string - as a documentation bug. "It hasn't changed recently, so we'll change the documentation to say it returns a string". I couldn't be bothered to argue

oh I’ve had the fun string vs integer return thing before

I did your commenting style 🙂