Skip to main content
You can define custom location-specific data types that can then be used in filters, such as to reject locations with a particular value. Or, this data can be used as a sort option in scenarios to compare the locations. This may be hourly rates, staff levels, or other attributes that apply to every location but may vary in value. Data types can also be populated in many APIs as a customData object with the configured name and a value appropriate to the data type. Custom Data Sets have been deprecated in the New Routing UI. Existing data sets configured in the legacy Routing UI will continue to be available and can be used in the New Routing UI. However, users will no longer be able to create or add new custom data sets from the New Routing UI.