Notifications

5 views

Description

Symptoms

A record has a number that doesn't fit the table prefix nomenclature. For example: an incident record has a number=5678890 instead of INC1234567.

Release

All releases.

Cause

The record is created from a list view that is generated by an invalid URL.

Viewing the log files at the time of record creation, I found the following:

    sysparm_referring_url=incident_list.do?sysparm_query=active%3Dtrue%5Enumber%3D5877500@99@sysparm_list_header_search=true@99@sysparm_first_row=1

That url is as follows:

/incident_list.do?sysparm_query=active%3Dtrue%5Enumber%3D5877500&sysparm_list_header_search=true&sysparm_first_row=1

 

If the record doesn't exist, you are presented with an empty list with a "new" button:

If the user clicks the new button to create a record, the fields included in the filter will be populated by the values, even read-only fields. This is what happened in this instance.

Resolution

This is expected behavior. One way to prevent this from happening is to write a before insert business rule that checks the format of the number field and aborts the insert if the format is incorrect.

 

Article Information

Last Updated:2019-08-02 20:36:49
Published:2019-07-22