Notifications

1048 views

Description

Records can be created or imported with a null sys_id. Modifying these null records can modify other task records with empty parent fields.

Steps to Reproduce

Perform the following steps on a non-production instance.

  1. Log in to an instance as an admin.
  2. Navigate to Incident > All
  3. Click on an incident Number to open a record.
  4. Click the menu icon  and select Export > XML (This Record).
  5. Open the XML file.
  6. Edit the sys_id to make it null (<sys_id>null</sys_id>).
  7. Save the XML file.
  8. Elevate your privileges by clicking on the small arrow next to System Administrator in the top right corner and selecting Elevate Roles.



  9. On the Elevate Roles popup, select security_admin.
  10. Click OK.
  11. Navigate to Incident > All.
  12. Right-click in a column header and click Import XML.
  13. Click Choose File.
  14. Navigate to and select the XML file.
  15. Click Open.
  16. Click Upload.
    Note that, in the Incidents list, you have two records with the same Number.
  17. View the sys_ids.
    1. Open one of the two records.
    2. Right click on the header bar.
    3. Select Copy sys_id.
    4. Paste the information into a text file. 
    5. Repeat steps 1-4 with the second record.
  18. Compare the sys_ids from the two records.
    Note that one record has a valid sys_id and one has a null sys_id. 

Workaround

This issue is under review. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also 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: PRB696038

Seen In

Fuji Patch 11 Hot Fix 2
Geneva
Geneva Patch 5

Fixed In

Jakarta Patch 8
Kingston Patch 2
London

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-07-12 10:49:23
Published:2017-07-26