I have a workflow action script that accepts two integer parameters. Just as an extra precaution, I also parseInt them. They represent a script ID and deployment ID. Despite this, for one user, suddenly the value keeps adding a .0 on the end. Nothing changed, it was working fine before. The only work around was to wrap it in a String. Why?

function goToSuitelet(context) {

      	var script_id = parseInt(runtime.getCurrentScript().getParameter('custscript_go_to_suitelet_script_id'));
      	var deployment_id = parseInt(runtime.getCurrentScript().getParameter('custscript_go_to_suitelet_deployment_id'));
    	var deployment_id = 1;
    	var params = {txid: context.newRecord.id};

    	redirect.toSuitelet({scriptId: script_id, deploymentId: deployment_id, parameters: params});

	}

I had to change the last line to

redirect.toSuitelet({scriptId: String(script_id), deploymentId: String(deployment_id), parameters: params});

I think your issue is it's trying to use "3312.0" and not "3312"

I would pass customscript_xxx and customdeploy_xxxx as the script and deployment id, instead of using the number internal id Because number internal id might be different between sandbox and prod, but you can control the "name" internal id

Have you tried removing

parseInt()

?

parseInt actually isn’t doing anything, as far as I can see (I logged out the value before and after the parseInt and neither had the .0), the .0 literally seems to be being added at the time that the argument is passed to the redirect. I’ve encountered this weird behaviour before. What’s ultra weird is that it’s not happening for everyone

Ya, I believe I've seen that issue before. I can't remember how it was resolved.

I think they only workaround is to wrap my (INTEGER!!!!) value in

String()

which forces it to be

"3312"

instead of just

3312

.

Well, whatever's clever 😂

the other place I’ve encountered this is returning a parameter of type List/Record and you are returning the internal id as an integer. NS will string it and you end up with 123.0 instead of just 123