Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Linking Fields to Share Values

We have a long list of 'Sites' in our Org that updates often. Separately, we employ several custom fields to list these Sites for use in dropdowns. It would be helpful if we could link a custom field to the Sites list, or any two fields for that matter, and have it automatically pull the up-to-date list from the other field. IE, a "Truck Relocation Request" form may require two custom fields for "Origin Site," and "Destination Site." Currently these two custom fields need to be updated any time the primary Sites list changes. We have 5+ 'Site' fields for catalog forms, increasing the chances one gets overlooked in an update.

Find more posts tagged with

feature request

Service Catalog

New Feature

custom fields

Status: None

Comments

Parm699

Hey there!

I totally get the hassle of manually updating multiple custom fields every time your Sites list changes. You can definitely link your custom fields to a primary Sites list to automate this process.

You might want to look into using lookup fields or dependent picklists, which can pull values from a master list. If you're using Salesforce, for example, you can set up a custom object for your Sites list and use a lookup relationship to pull those values into your forms.

This way, whenever your main Sites list updates, all the linked custom fields will automatically reflect those changes. It'll save you a ton of time and ensure consistency across your forms.

Hope this helps!