404 views

Description

Records in the sys_storage_alias table are not deleted when dropping a field from an extended table via an update set commit.

Steps to Reproduce

 

 

  1. Import, preview, and commit an update set that includes two field creations named u_new_field, one on the incident table (extended) and one on the sys_broadcast_message table (not extended).

    For more information, see the documentation topic Update set administration.

  2. Verify that the corresponding records in the sys_dictionary and sys_storage_alias tables have been created for both fields. The following pieces of code return true:

    gs.print(GlideTableDescriptor.fieldExists("incident", "u_new_field"));
    gs.print(GlideTableDescriptor.fieldExists("sys_broadcast_message", "u_new_field"));

  3. Import, preview, and commit an update set that includes the deletion of both fields.

    Expected result:
    The records for both fields in the sys_dictionary and sys_storage_alias tables are deleted and the following pieces of code return false:
    gs.print(GlideTableDescriptor.fieldExists("incident", "u_new_field"));
    gs.print(GlideTableDescriptor.fieldExists("sys_broadcast_message", "u_new_field"));

    Actual result:
    Only the record in the sys_dictionary table is deleted.
    gs.print(GlideTableDescriptor.fieldExists("incident", "u_new_field")); // returns true when it should be false
    gs.print(GlideTableDescriptor.fieldExists("sys_broadcast_message", "u_new_field")); // returns false, which is correct

Workaround

Contact Customer Support to remove the problematic records.


Related Problem: PRB900722

Seen In

Helsinki Patch 5
Istanbul Patch 5 Hot Fix 1

Fixed In

Istanbul Patch 6
Jakarta

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-01-04 08:21:37
Published:2017-05-08