Use of secure insert multiple operation within import set API

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Use the com.glide.import_set_api.insert_multiple_optimize property to control whether GlideRecordSecure or GlideRecord is used for the Insert Multiple operation within the Import Set API.

    The com.glide.import_set_api.insert_multiple_optimize system property controls whether GlideRecordSecure or GlideRecord is used for the Insert Multiple operation within Import Set API.

    If this property is set to false, then GlideRecordSecure will be used to insert records and Table level ACLs will be evaluated.

    If this property is set to true, then GlideRecord will be used to insert records and Table level ACLs will not be evaluated.

    Ensure that the property com.glide.import_set_api.insert_multiple_optimize is set to false.

    Note:
    If this property must be set to true, then you must ensure that the Import Set API Insert Multiple REST Endpoint ACL (sys_id: 3101b770ff2211105cf343d0653bf182) is active and also audit user's who have the import_transformer role.

    More information

    Attribute Description
    Configuration name com.glide.import_set_api.insert_multiple_optimize
    Configuration type System Properties (/sys_properties_list.do)
    Data type Boolean
    Recommended value false
    Default value <none>
    Fallback value false
    Category Access control
    Security risk
    • Severity score: 6.5
    • CVSS score: Medium
    • Security risk details: If this property is not set to the recommended value of false, then a low privilege user may be able to insert data into tables outside the scope of their privileged roles.
    Dependencies and prerequisites None
    Functional impact This property optimizes the performance of Import Set API by using GlideRecord to save data. When the parameter is set, it requires an integration user to have the import_transformer role to access the API.
    References https://developer.servicenow.com/blog.do?p=/post/gliderecord-vs-gliderecordsecure