We recently did a CSV import of Credit Memos, where the only thing the import was doing was setting the value of two newly created custom fields. These custom fields do not do any sourcing. We’ve now noticed that for records that were updated during the import, if they were applied to Invoices, they are now no longer applied. This is obviously disastrous. There’s no reason the import should have had this effect. Has anyone experienced similar?

Haven't seen this for credit memos explicitly, but I had the exact same issue with zero dollar "payments" at a prior company. Was a giant PITA because we had thousands and thousands of them. The challenge is that when there's a zero dollar payments there's no actual record tying the invoice and the other paying transaction (often a JE in our case) together. It just updates the status of both, and so whenever you edit that record, it breaks that and undoes the zero dollar payment. Only solution I found once it happens is to redo the zero dollar payments, making sure to do any other edits that you need to do first. One thing that did help a little, was modifying the pay bills page/sublist so that I could filter to just the things I needed. IIRC I actually put a custom field on all the things I edited to identify them on that page and then paid them all together.

I've run into that with JEs that are applied to stuff too; that literally any edit of the JE will unapply it, which is a PITA. I've never seen it happen on other transactions though. Unless maybe it was a line item field? Can also commiserate, but I don't think there's much you can do unfortunately other than figure out how they were applied and re-apply them via CSV. I'd be curious once everything is fixed if you go into a Sandbox and do manually in the UI what you did via the CSV import if it gives you a "hey this change is going to unapply stuff" message.

Interesting. Did it manually and it unapplied but didn’t SAY it would.

> I hate everything Ah the NetSuite Admin credo. Seriously though, I might file a case with NetSuite on this. You piqued my curiosity, so I hopped into my own Sandbox and tried this and to use support's favorite terminology "I was unable to recreate the issue in my environment." I tried changing 1 each of a native and custom header field and 1 each of a native and custom line field. It didn't unapply during any of those tests. Maybe some weird bug got introduced into your account somehow. JEs are weird about that, but I've never run into any other transaction unapplying unless I modified dollar amounts obviously. Doesn't help you today, but I'd totally complain about this one for the future.

Did you uncheck run scripts/workflows? I've also seen anything on the line level causing problem esp when custom pricing is involved.

Yes I unchecked, I always uncheck 😉

turns out it didn’t do it on ALL the imported records

Well that's even more perplexing. I'm curious what the culprit turns out to be.

Have you checked if the posting period for the 19 is already closed?

It is closed, but it’s also closed on the ~2000 other records we set the new field value on, and those didn’t unapply themselves.