Data Lookup Definitions-->Setter Field Definitions is not populating Source table fields & Matcher table fields in fuji release

mallikarjunared · ‎04-02-2015

Hi Team,

Sub: Data Lookup Definitions-->Setter Field Definitions is not populating Source table fields and Matcher table fields in fuji release.

I am facing this issue in fuji demo versions. For example (https://demo021.service-now.com/navpage.do).

Create table test--extends dl_matcher ( Data Lookup Matcher Rules).

Navigate to Sys policy--rules--data look up definitions-- New--data look up rule

Name--AAA

Source table---change request

Matcher table---test -->save it. Once done, open matcher field definitions and map them. open setter field definitions.

Here is the problem, unable to map fields between source table and matcher table.

Please let me know the reason, why I am not able to see drop down fields in setter field definitions. Previously it is working with Eureka. I tried in other demo versions also, no result except in https://demo019.service-now.com/navpage.do . Data Lookup and Record Matching Support plugin is already activated.

Please help me in this issue.

Thanks & Regards,

Mallikarjuna Potha

dwolf · ‎05-04-2015

The work around Gigi Sossi is recommending is this:

- Go to UI Policy and reverse the Policy with the Short Description "Hide matcher table and source table" for the Setter Field Definitions [dl_definition_rel_set] table.

- Open the data lookup definition that is not working and create a new "Setter Field Definition".

- Right click on the Form header and choose Configure > Form Layout (or Form Design) and add the following fields:

> Source table

> Matcher table

The source table field & matcher table field should now let you choose the fields you would like to set.

View solution in original post

Erich Zirnhelt · ‎05-20-2015

Hi Mallikarjuna - once the Known Error article is published, we'll share the link as part of this Product Issue thread.

mallikarjunared · ‎05-20-2015

We will wait for your response. Thanks Erich

Erich Zirnhelt · ‎05-25-2015

Hi Mallikarjuna Potha - in case you did not notice it, there's now a link to the associated Known Error article at the top of this thread.

Thanks again for your help!

geomathew · ‎05-14-2016

I tried the work around in Eureka and it works fine however in my Geneva dev instance it is not working. I think the work around is not consistent across the versions.