How the “Is Deleted” functionality works

The “Is Deleted” mechanism uses two key fields that have default values when a record is first created or when the scoped app is installed:

• Is Deleted: false
• Data Token: (DEFAULT)

First cycle: Initial normalization

• During the first cycle, all records that are updated by the normalization process receive a new timestamp in the Data Token field.
• These records are considered current, so the Is Deleted flag remains set to false.

Second cycle: Detecting deletions

• In the second cycle, new or updated records from the Data Platform or IT Visibility are processed and assigned a fresh Data Token.
• The system then applies a filter to identify records that may have been removed from the source data. The filter looks for records where:
• Data Token is not set to the default value.
• Is Deleted is currently false.
• Data Token does not match the current import’s token.
• Data Source matches the source of the current import.
• Records that meet all these conditions are considered missing from the latest import and are therefore marked with Is Deleted = true.

Filter condition example

var expressionv2 = 'x_fls_flexera_fnms_data_token_v2!=(DEFAULT)' +

                   '^x_fls_flexera_fnms_is_deleted_v2=false' +

                   '^x_fls_flexera_fnms_data_token_v2!=' + data_token +

                   '^x_fls_flexera_fnms_data_source_v2LIKE' + DataSource;



var expression = 'x_fls_flexera_fnms_data_token!=(DEFAULT)' +

                 '^x_fls_flexera_fnms_is_deleted=false' +

                 '^x_fls_flexera_fnms_data_token!=' + data_token +

                 '^x_fls_flexera_fnms_data_sourceLIKE' + DataSource;

Final outcome

• Records no longer found in the latest import are flagged as Is Deleted = true
• Records updated or still present have Is Deleted = false

Tables supported by the is deleted functionality

The functionality applies only to these tables:

• cmdb_ci_computer
• cmdb_ci_disk
• cmdb_ci_network_adapter
• cmdb_sam_sw_install
• x_fls_flexera_fnms_normalized_software_instances
• cmdb_ci_acc
• cmdb_ci_building_facility
• cmdb_ci_facility_hardware
• cmdb_ci_generator_power_eq
• cmdb_ci_hvac
• cmdb_ci_ip_firewall
• cmdb_ci_ip_phone
• cmdb_ci_ip_router
• cmdb_ci_lb_network
• cmdb_ci_mfp_printer
• cmdb_ci_msd
• cmdb_ci_netgear
• cmdb_ci_peripheral
• cmdb_ci_power_eq
• cmdb_ci_printer
• cmdb_ci_printing_hardware
• cmdb_ci_rack
• cmdb_ci_tape_server
• cmdb_ci_wap_network

Records in tables not listed here are not considered by this functionality.

Scenario example: software installation lifecycle

First cycle: initial import

When data is first normalized and imported from Data Platform, new or updated records have Is Deleted set to false and share the same Data Token for that import run.

Import run

Software installation

Example of a software installation record inserted with Data Token “1664179926”:

Second cycle: software removal

If the software is manually uninstalled or removed from the source, the next import run updates the Data Token for current records. Records that no longer match the filter condition are marked as Is Deleted = true.

Import run

All the corresponding records that were inserted/updated with this import run will hold the same Data Token as this record.

Software installation

If any records from the table and filter condition matches, then it will set the Is Deleted field to true.

Third cycle: software rediscovery

If the software is rediscovered and imported again, its record is updated with the current Data Token, and Is Deleted is reset to false.

Import run

All the corresponding records that were inserted/updated with this import run will hold the same Data Token as this record.

Software installation

If the software is rediscovered, it will be updated with the current Import Run’s data token and the Is Deleted flag will be set back to false.

This feature:

• Accurately identifies and flags records removed or missing from the source without physical deletion
• Keeps the CMDB clean and current
• Automatically restores records if rediscovered in future imports
• Enables improved lifecycle tracking and audit compliance