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

[mallikarjunared]

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 · Accepted solution]

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.

[stevejarman]

Is anyone able to expand on this "workaround"? I've followed this, and I'm able to add those additional fields (Source table field and Matcher table) to the form (and they show the correct information), but that doesn't resolve the issue - i.e. I'm still unable to select values for the original fields to create the rule. Is there an additional step missing? Maybe something that's no so obvious to a fairly new user such as myself?

[mallikarjunared]

Thanks Darlene, issue is resolved. Once again thanks to everyone

[BenPhillipsSNC]

Hello All,

I wanted to state that we have an existing PRB for this issue: PRB627598, and because of you all, I have now documented the workaround from this thread into the PRB! I am requesting to have the related KB published soon. Thank you all for your work.

[mallikarjunared]

Could you please provide me the link for this prb? I will go through this once