Breadcrumbs

Update First Seen (Discovered) on Update of CIs in ServiceNow

Connector Applicability

Applies to Source Connectors

  • Microsoft Defender for Endpoint

  • InTune

  • JAMF

  • Lansweeper On-Prem

  • Lansweeper Cloud

  • Omnissa Workspace ONE

Applies to Destination Connectors

ServiceNow

Assumptions

These instructions assume you have already setup a source connection in CI Sync for ServiceNow.

Pre-Read

Syncfish recommend customers read the following documentation before changing the Connection Setting/s described below.

  1. Understanding the use of CI Sync Connection Settings

  2. Rule 9 - Update First Seen (Discovered) Attribute for CI Update Operations in ServiceNow

Locating and Amending the Connection Setting in the CI Sync UI

  1. Navigate to the Settings pageNavigate to the Settings pageNavigate to the Settings page

  2. Under the Destination Connections heading (list), locate your ServiceNow connection (it will be either a Non-PROD “TEST” connection or the “PROD” connection depending on which one you need to amend).

  3. Click the Update link on the right hand side of the ServiceNow connection.

  4. Scroll down and locate the Additional Settings Heading and view the Individual Connectoin Setting related to this guide.

CleanShot 2025-11-16 at 14.57.15@2x-20251116-050409.png

The screen shot is provided only as sample to assist when reading this page. The state of your own CI Sync UI will depend on whether you are starting from the CI Sync default position or if you have already amended one/more of the settings.

  1. Tick the Override default box/boxes and then use the sliders related to the individual settings. The following table elaborates any further information about these particular settings.

Setting

Type

Additional Notes

Update First Seen

Slider

When enabled (the default), the first_discovered attribute is updated during CI Insert and CI Update operations.

When disabled, the first_discovered attribute is only updated during CI Insert operations.

  1. After modify the settings, scroll to the bottom of the page, tick the “I consent…” checkbox and finally click the Save connection button.

  2. You can now run a sync job and the amended settings will be applied causing the CI Sync Data Sync rules to be modified accordingly.

Importantly

Make sure you consciously override the setting against either your TEST or PROD environment (i.e. your TEST vs PROD sync jobs).

For more information on how to use TEST vs PROD Connection Settings please read Understanding the use of CI Sync Connection Settings.

Syncfish strongly recommend making changes for TEST environment/sync jobs first. Only modify PROD related settings after thoroughly validating the intended results in TEST.