→ Celebrate SysAdmin Day 2024 with Lansweeper Enter our Giveaway here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
sophie
Lansweeper Tech Support
Lansweeper Tech Support

TL;DR-Sweepy-Icon (1).png
Sync custom fields between Lansweeper On-premises and Lansweeper Sites. This guide covers benefits, requirements, and tips for seamless data integration and migration.


Synchronizing your Lansweeper On-premises custom fields with Lansweeper Sites enhances asset management, offering increased flexibility and control. This process allows you to include custom fields in views, reports, and API-based integrations without field limits. This feature is beneficial if you’re using both Lansweeper On-premises and Lansweeper Sites, as it enables you to automate asset data migration and allows day-to-day operations to shift smoothly to Lansweeper Sites.

Benefits

  • Include custom fields in views and reports: Use custom fields to filter data in custom views and reports.
    Custom fields in reports are only available for cloud-first installations and hybrid installations with custom field sync enabled. Hybrid installations without custom field sync cannot use custom fields in reports.
  • No field limits: Lansweeper Sites support unlimited custom fields, unlike Lansweeper On-premises, which supports up to 20 custom fields per installation.
  • Custom fields in integrations: Include custom fields in your integrations for enhanced data management.

Requirements & considerations

Enabling custom field synchronization is irreversible. After enabling custom field sync, it cannot be disabled.

Before syncing your Lansweeper On-premises custom fields with your Lansweeper Site, keep the following points in mind:

  • Irreversible sync: Once enabled, custom field sync cannot be disabled.
  • One-way sync: The sync is one-way, from Lansweeper On-premises to Lansweeper Sites.
  • Required permissions: Only site owners can enable custom field sync.
  • Pre-sync review: Review your existing custom fields before syncing. Ensure you’re satisfied with the Name and Type of each custom field, as these attributes are synced only once. If you need to edit your fields after enabling sync, you must manually update them in both your site and on-prem installation.
  • Multiple installations: If you have multiple Lansweeper On-premises installations, review the custom field sync rules.

Multiple Lansweeper On-premises installations

If you have multiple Lansweeper On-premises installations connected to a site, all custom fields across these installations will sync to your Lansweeper Site and become global fields.

Review the custom fields for each installation to ensure they comply with the custom field sync rules.

Custom field sync rules

These rules apply to all installations connected to a site:

  • Same Name and Type: Fields with the same name and type will be combined into one. For radio button lists, combo boxes, and Yes/No values, they will become a dropdown with all values added as options.
  • Same Name, different Type: Fields with the same name but different types will create separate fields.
  • Slot ID: The Slot ID does not affect synchronization and is not included in your site.
  • Case and character sensitivity: Fields are case-insensitive (e.g., "po" and "PO" are the same) but character-sensitive (e.g., "P.O." and "PO" are different).

Sync your fields

  1. In your Lansweeper Site, go to Configuration > Site settings.
  2. Under Sync asset fields from on-prem to your site, select Custom fields from the list.
  3. Select Sync my data.
  4. Confirm whether you’re ready to sync your custom fields. Remember, once sync is enabled, it cannot be disabled.
  5. Select Enable custom fields sync.

Navigate to your inventory. Once the sync is complete, a confirmation message will appear.

Manage custom fields

Decide whether to manage your custom fields in Lansweeper On-premises or Lansweeper Site. Custom fields and their values only sync from On-premises to your site, so changes made on your site won't reflect in On-premises.

On-premises management

For managing custom fields on-premises, refer to Configure and add data to asset custom fields.

Manage custom fields in your site

Once the fields are synced, you can view and manage them within your Lansweeper Site.

Any changes you make to your custom fields in your Lansweeper Site are NOT synced back to your on-prem installation. If you manage your asset inventory on-premises, edit custom fields there.

  1. Go to Inventory > Manage custom fields.
  2. View, edit, delete, or add new custom fields.

Edit your assets' custom fields in your site

Any changes you make to the value of your custom fields in your Lansweeper Site are NOT synced back to your on-prem installation. If you manage your asset inventory on-premises, edit custom field values there.

  1. In your Inventory, find the asset you want to edit from the list and select the asset.
  2. Select Edit asset.
  3. Navigate to the Custom fields section.
  4. Edit the custom fields as needed.
  5. Optionally, select the option to Lock against edits from on-prem. If you lock the field, the value you assign to it will not be overwritten by values assigned on-prem. This is useful if you’re planning to manage your inventory from your Lansweeper Site or if you need the values between your site and on-prem installation to be different. If you do NOT lock against on-prem edits, any changes you make to the value of that field in on-prem will sync to your site.

You can also bulk edit values for your custom fields:

  1. Select the assets you want to edit.
  2. Select Bulk edit assets and choose your custom field from the list. Fields can be locked against on-prem updates from here as well.
Was this article helpful? Yes No
No ratings

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now
Version history
Last update:
3 weeks ago
Updated by: