663 views

Description

When you create two data lookup definitions and tables with the same source, the lookup will work for only one of the definitions but not for both.

Steps to Reproduce

Reproducible on a Calgary demo.

  1. Install the Data Lookup plugin (include demo data)
  2. Create new dl table called dl_u_impact.
    For more information, see Create custom data lookups
  3. Base Category and Impact fields off of the same fields in the incident.
  4. Create a record for the new table: Category = request, Impact = 1
  5. Create new Data Lookup Definition Records: Source table = incident, Matcher table = dl_u_impact
  6. Set all run on to true.
  7. Create Matcher definition: Source table = category, Matcher field = category
  8. Create Setter definition: Source = Impact, Matcher = Impact, Always replace = true
  9. Create a new incident. Change category to request.

This should change impact to 1 and the Assigned to to Fred Luddy (note the base system dl definition: Assignment Lookup).
This does not occur. Usually impact changes but Assigned to does not.

If you look at the xmlhttp.do request, you will see the return is not complete:

Correct return for Priority:
<?xml version="1.0" encoding="UTF-8"?><xml sysparm_max="15" sysparm_processor="AJAXDataLookup"><item label="3 - Moderate" name="priority" value="3"/></xml>

Incorrect return for Category:
<?xml version="1.0" encoding="UTF-8"?><xml sysparm_max="15" sysparm_processor="AJAXDataLookup"/>

 

Workaround

The only workaround possible is to use a client script instead of the data lookup for one of the definitions.


Related Problem: PRB584334

Seen In

Berlin Hot Fix 4
Calgary Patch 1
Calgary Patch 3 Hot Fix 1
CCA 6
Dublin EA 8
Dublin Patch 1 Hot Fix 1
Dublin Patch 2
Dublin Patch 4
Dublin Patch 6
Eureka Patch 11 Hot Fix 2
Eureka Patch 3 Hot Fix 1
Eureka Patch 6
Eureka Patch 7

Fixed In

Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-10-30 12:22:12
Published:2017-10-30