Has anyone encountered a bug where for some but no...
# suitescript
j
Has anyone encountered a bug where for some but not all users, url.resolveRecord appends
.0
to the ID in the returned URL? For example, for me, I get
/app/common/custom/custrecordentry.nl?rectype=98&id=6058&compid=<ourcompid>
but another user gets
/app/common/custom/custrecordentry.nl?rectype=98&id=6058.0&compid=<ourcompid>
e
probably the script passing the parameter as integer or something along those lines. doesn’t really explain why for some users and not others though. try logging the value you are passing to the parameters / id and inspecting it
j
script isn’t passing a parameter.
looks like it randomly stopped doing it for the user today.
e
yipee! just kidding. what does your full url.resolveRecord call look like? can you share?
j
Copy code
var tx_url = url.resolveRecord({recordType: record_type_lookup[results[r].type], recordId: results[r].id});
(the arguments are correct, worked fine for all other users)
I’ve had this
.0
issue crop up intermittently in NetSuite a few times over the years
though this is the first time it’s manifested in url.resolveRecord