548 views

Description

When a Reference field is dependent on another field, results are not being limited as expected in addition to the reference qualifier, if the field it is dependent on is not present in the form layout.

This is working as expected when list editing a dependent Reference field, but not when editing the field on the form.

The same behavior occurs if setting the Incident Watchlist as dependent on the Company, so that, when clicking on the reference lookup for the watchlist, only users under a certain company should be listed.
 
When removing the Company field from the Incident Default View, or using the the Self-Service view where Company is not displayed, the watchlist reference lookup shows to all the users.

Steps to Reproduce

  1. Login as admin on any instance
  2. Open any incident record and make sure Company is on the form
  3. Right click on Watchlist > Configure Dictionary > Check [Use dependent field] > Select Company as dependent field > Save
  4. Navigate back to incident form in Default view and make sure Company field is populated with a value
  5. Click on Watchlist field and do a lookup, only see users under the specified company
  6. Right click on the incident form > Configure > Form layout > Remove Company from the view
  7. Navigate back to incident form in Default view and click on Watchlist field and do a lookup, see all the users
  8. Navigate back to incident form in Default view and change the view to Self-service
  9. Click on Watchlist field and perform a lookup, see all the users
  10. Right click on the form > Configure > Form layout > Add Company to the Self service view
  11. Navigate back to incident form in Self service view, and click on Watchlist field and perform a lookup, only see users under the specified company

Workaround

This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.

Related Problem: PRB601488

Seen In

Berlin Patch 4
Dublin EA 8
Fuji Patch 4 Hot Fix 1
Helsinki Patch 2
Helsinki Patch 3 Hot Fix 3

Intended Fix Version

Madrid

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-08-02 00:26:57
Published:2017-11-27