topic Sequencers - Zero Pad Auto Generated Numbers in Fusion Manage Forum

Sequencers - Zero Pad Auto Generated Numbers

Anonymous — Mon, 08 Oct 2012 20:25:48 GMT

I am getting errors in my script for my custom auto part numbering.

I am using a script to define a prefix for my part number then select the correct sequencer to use for that prefix family.

That all appears to be working correctly. The error is coming from the libray script SequencOperator. In need to have the next sequence number generated zero padded and if I check the check box on the sequencer I get the following error.

"[sequenceOperator (line 25, col 0)] org.mozilla.javascript.EcmaError: ReferenceError: "padding" is not defined. (sequenceOperator#25)"

Attached is the autonumber script and the definition of the sequencer I am testing. The code is incomplete as not all the possible prefix 'CASE' statements are included as I am currently testing the validity of the script logic.

Any help is appreciated as the script works fine as long as I don't check the zero pad check box on the sequencer

Thanks,

Bob Donovan

Bigge Power Constructors

Re: Sequencers - Zero Pad Auto Generated Numbers

Anonymous — Mon, 08 Oct 2012 21:22:33 GMT

Hi Bob,

I have also found the same issue, and am looking into it right now.

It seems that the issue is in the sequenceOperator Script...

Anonymous — Mon, 08 Oct 2012 22:56:14 GMT

It seems that the issue is in the sequenceOperator Script

The padding variable of the ZeroFill function is not being passed correctly.

Need a defintion of something line

var padding = SeqGenerator.Length

Re: It seems that the issue is in the sequenceOperator Script...

Anonymous — Mon, 08 Oct 2012 22:59:53 GMT

I added that var statement to the sequenceOperator Script and it is now working correctly.

Not sure if this was an issue with my tenant or all tenants since the sequenceOpertator Script is part of the base tenant.

Any feedback?

Re: It seems that the issue is in the sequenceOperator Script...

Anonymous — Tue, 09 Oct 2012 12:46:41 GMT

Hi Bob,

We did find this as an issue with all the tenants and will be rolling out an update for everyone.

Thanks for bringing this to our attention.