Notifications

168 views

Description

Auto-number fields such as the number field in a Task-based record (such as Incident, Problem, Change) have wide gaps. This issue is more noticeable if List v3 is active. The counter gets incremented when the List v3 condition builder is loaded.
 

Steps to Reproduce

Note – Perform these steps only during periods of low activity or in a development instance. In an environment where users are actively creating incident records without submitting them, the number record will change and the issue is harder to observe.

  1. Verify that the List v3 Components plugin is active.

  2. Open the sys_number_counter record for the Incident table and note the number.

  3. Open a report on the incident table using the Report Designer.

  4. Once the report has fully loaded, reload the sys_number_counter record.

    Note the increase in number.

  5. Use the browser to refresh the entire report page, and wait for the report to fully load again.

  6. Once the report has fully loaded, reload the sys_number_counter record.

    Note the increase in the number. Increases should not occur when a report is loaded or the condition builder is expanded.

With the List v3 Filter active

  1. Verify that the List v3 plugin is active.
  2. Open the sys_number_counter record for the a table where List v3 is active, for example, Incident. Note the number.

  3. Navigate to the incident table.

  4. Click the Antenna icon at the top left to display the condition builder.

  5. Once the incident list has fully loaded, load the sys_number_counter record again.

    Note the increase in number.

  6. Use the browser to refresh the list page and wait for the report to fully load again.

  7. Display the condition builder.

  8. Once the list has fully loaded, load the sys_number_counter record again.

    Note the increase in number. Increases should not occur when a report is loaded or the condition builder is expanded.

 

Workaround

All records in the instance are referenced by a system-generated and instance-wide unique sys_id value. The number fields are used as a human readable reference number and are not intended to be contiguous. Gaps in number fields are expected and have no impact on system functionality.

There is no maximum or reset point for numbers. If a length of 10 has been specified and enough records have been created, the next number will increase past the specified length.  For example, INC9999999 will roll up to INC10000000 even though the length of 10 was specified originally. For more information, see the product documentation topic Record number field type.

You can manage record numbering as described in the product documentation topic Add auto-numbering records in a table but this functionality is recommended only if you are in an industry where accounting for numbering gaps is necessary.

If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

While an upgrade is not possible, the workaround consists in preventing all uses of the condition builder v3:

1. Turn off the new report designer.
2. Turn off List v3.
3. Do not use Performance Analytics, which adopts the condition builder v3 in the forms.
4. Check which other user groups that could have turned on the condition builder v3 in their forms. All users or customers would need to switch off the condition builder v3 from any platform forms that have it turned on.

 


Related Problem: PRB1265733

Seen In

There is no data to report.

Fixed In

Jakarta Patch 9
Kingston Patch 5
London

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-06-08 01:00:06
Published:2018-06-08