Someone delete a transaction?
# general
k
Someone delete a transaction?
s
Yes, but more than likely we have deleted a lot more than just one transaction
Eh, found the preference that does not include transaction numbers in the Global Search.... That seems to do the trick.
k
That works, but might have unintended consequences elsewhere if you have transacting numbering configured
When NetSuite added that preference, they defaulted it off, so someone made decision to turn it on
s
Hmmm you're talking about with aut-generated numbers, right? But those are for Document Number and not necessarily the Transaction Number, right?
I'm just trying to think of a situation where we would search for a system-generated transaction number.
d
i've run into this issue before, where the transaction number does not match the document number, netsuite basically said they're not guaranteed to be in sync. And there was another field for me to use instead... let me dig around and see if i can't find the results from that ticket. my issue was with item fulfillment records though
s
Ah that's so friggin silly... Well, if you were able to resolve the Item Fulfillments, I think I should be able to resolve Invoices, since at least those are able to be updated via CSV
Thanks so much @dbaghdanov
d
oh, looking back, it appears i had a mis-match between tranid & transactionnumber, where one was named,
Item Fulfillment #IF-12345678
, but the other was
IF-12345677
s
YES
That's exactly what's happening with us
d
where here was the first part:
Based on our engineers, the encountered behavior is as expected since the transaction number and document number are independent numbers. Upon creating a transaction, the transaction number is assigned based on the numbering setup and right after the transactionnumber generation, the same happens with the document number and independent document number sequence.
If there are two transactions created at the same time, there is a possibility that the second transaction gets earlier to the process of assigning the document number.
The suggested workaround is to incorporate some delay into the script to prevent the occurrence of having two transaction generated at the same time but we still cannot guarantee that the numbers will be the same.
🤢 2
but that was a BS solution, let me keep looking, there was something better....
s
LOL what kinda solution is that
Hahahaha appreciate the looking David!
d
this was a good one too: 🙄
Case: 3114376: Defect 503951 : Item Fulfillment the tranid shows one value, and the transactionnumber an incorrect value
Status Change:
Status changed from Open - Under Investigation to Closed - As Designed
🤢 2
s
Ooooo I bet it's an enhancement request that will never get looked at
d
I think in the end, we ended up using the 'Transaction Number' field, now this was in a saved search
s
One thing I mentioned here is disabling the preference for Global Search Includes Transaction Numbers
I feel like that way, you are looking exclusively at doc num
message has been deleted
d
mine is unchecked also, i'm trying to find the search that this was on, because it was an interesting field
I found a note of mine:
when creating an Item Fulfillment search, you should not be using the Document Number (like I’ve done before) and instead use the Transaction Number, which returns the tranid , which is the IF-123456789 number.
gosh i hope this helps
s
Ah I gotcha my man. Really, this issue was specifically for the Global Search. That being said, I super appreciate you looking through your notes! 🔥🔥🔥
d
i think you're issue is similar in a sense, when netsuite generated different transaction numbers, and document numbers (for the same transaction record), they both showed up in the global search as well
s
Yeah, it's definitely similar. But I guess, I just don't really understand how we can start using the transaction number, if that makes any sense - when the Document Number is what is shown in the UI. To get the Transaction Number and start using it would be kind of a pain, don't you think? You would have to go to the XML every time, and even then, since there is no setting to disable the Doc Nums from the Global Search, you would still run into an issue where you're pulling two different transactions with the same number.
Maybe I'm missing something though....
d
no i get you, you run a global search for invoice 123456 and get back 2, then you're like great, which one is the real one
in our case we only ran into duplicate numbers randomly, i remember creating a saved search to find duplicates and send an email alert, but after several months it only triggered a few times
k
Maybe you could turn on "allow override" and script an update process
for managing the mismatches
only problem is if you have automatic notifications for customers that includes the number that's no longer accurate.
Also - your mismatch process to script it would have to change the number on one of the two inverted to a temporary number
and then update all the others
in the right sequence.
lot of work there.
s
Yeah I was thinking about that - not sure if it's worth it, since we easily have over one million invoices
k
Sounds like a bad idea.
s
Think we're gonna just go with this preference for now... I'm really thinking that might be the solution
Appreciate both of ya'll @KevinJ of Kansas and @dbaghdanov
👍 2