Notifications

3419 views

Description

Product documentation describes how to renumber tables; however, this is intended for Task extended tables that use the 'number' field. Use the workaround below for renumbering custom tables or other tables that use a non 'Number' field for numbering records.

Steps to Reproduce

 

  1. Follow steps as described in Managing Record Numbering in product documentation for a custom table.
  2. Notice that upon changing the number of digits, the existing records do not change.

Workaround

  1. Duplicate the base system business rule named Pad Numbers by clicking the Insert and Stay button. (If Insert and Stay is not available on your instance, you can create a new business rule and manually copy all the field values from Pad Numbers.)
  2. Give the business rule a new name and change the script field to read as follows:

    padCurrentCategory();
    function padCurrentCategory() {
    var target = new GlideRecord(current.category+"");
    if (!target.isValidField("u_number") || target.isValidField("number")) return;
    var nm = new UNumberManager();
    nm.padTableNumbers(current.category, current.maximum_digits);
    }

  3. Save your changes.
  4. Duplicate the base system script include named NumberManager.
  5. Change the following two lines as indicated:

    105: currentNumber = records.u_number.toString();
    117: records.u_number = prefix + currentNumber;

  6. Name the new script include UNumberManager and save your changes.
  7. Follow the instructions in the product documentation.


Note: Subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

 


Related Problem: PRB578359

Seen In

Aspen Patch 6
Calgary Patch 2 Hot Fix 10

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-11-10 07:39:53
Published:2014-12-08