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

mallikarjunared
Tera Contributor

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

1 ACCEPTED SOLUTION

dwolf
Giga Expert

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

13 REPLIES 13

gigi3
Mega Contributor

Hi to all


I have Exactly   the same problem after fuji upgrade to Patch 2 hotfix 1



Let me know if anyone have some feedback.


In the meantime I opened a ticket


Giovanni


gigi3
Mega Contributor

Hi,


try to include source_table and matcher_table in the Frorm Layout


Giovanni


Did it worked for you? I am not getting the point what you are saying, could you please explain it more clear???


Hi Gigi,



I was having the same issue.



I can report that adding the source_table and matcher_table fields to the form fixes the issue.



Both are hidden on the form, so there is no visible difference, but the Source table field and Matcher table field now populate.



Thanks for the suggestion