(retrying) what's the deal with the p/n ref field ...
# suitescript
k
(retrying) what's the deal with the p/n ref field on a customer deposit? its behavior is weird enough that i'm not sure if it's supposed to be used in this way. i can't seem to create a CD that contains a
pnrefnum
in standard mode. i'm recording/representing a payment made on an external site i know that i can create my own field, but for ease of migration, my customer uses this field already in various things so it'd be good to be able to set it correctly
a
based on this from the records browser I'd say
pnrefnum
is effectively a system field you should not be setting yourself, seems weird you can set it in the UI though.
Copy code
If you accept credit card payments, the Verisign authentication code appears here once the payment is approved.
k
that's why i'm a bit sus about it, however:
a
if you're taking payments in an external system, then the auth would be in that system, not NetSuite, so having the auth code here would be kind of weird. again based on the records broswer entry for
ccapproved
I think you'd just check that and call it done. if you want your own ref number for it use a custom field which you were already thinking about.
k
when you check "CC accepted", this is supposed to mean (apparently) that a CC was charged externally, and you can set the ref num
that's why it works in the UI
if i reproduce a very fragile set of steps, i can get it to create a record with the reference number set in dynamic mode, but i'm trying to avoid dynamic mode -- and this behavior makes me a bit nervous about relying on it
weirdly the record created this way does not have a "payment event" anymore either
a
... okay i was gonna say if it works in the UI you could maybe do it in dynamic mode .. sounds like you're there already
k
yeah. i'm just trying to understand why because i don't trust what i'm seeing to work consistently
there's either a better way to do it, or i should be doing something else -- but i can't find out why it's behaving this way so it's difficult to make that call
a
yeah i think there's more complexity here, and NS is waving it away, i remember trying to generate payment events using suitescript and it was nightmare, but this was years ago so my only takeaway was - avoid this in the future 😄
I think you're exactly where you need to be, if you can test it to your satisfaction then go ahead with the dynamic mode, if you're just not getting comfortable with that, forget the whole thing and just set that value in a different field for reference
it seems sus, cos its sus 😄
k
😞
any idea if there's someone hanging around here who'd know in more detail? i don't like not understanding
meanwhile i'll follow up with the client and see what to do
a
I can't think of anyone specifically that worked with this a lot, I think the reason no one jumped in to help is cos maybe we all feel a little bit this way about how NS handles this process.
👍🏻 1
k
hah
i thought maybe it was holiday weekend stuff and then there was a lot of posts pushing it off screen 😉
i appreciate you taking the time to respond though
👍 1
a
good luck, you might be right, maybe everyone will run in here help later today 🙂
k
if they don't skip it seeing a response 😂
though i have to say, of the "community support" chats i've seen, this is one of the best i've encountered for getting answers - i didn't initially expect much considering it looked like just another corporation shunting the responsibility for support onto "the community" 😉