- is the object matching working in general (see if it works in the object workspace)? Or do you get an error here as well?
-> Does it work in other object matching lists (e.g. Knowledge, Problem)?
- Are you able to see/modify the object matching properties in the business object layout?
Can you also please
- try to disable and re-enable the object matching once in the Incident Layout and see if it works?
- run the following query and see if it returns results:
SELECT Name, DisplayName, Definition FROM Frs_def_object_matching WHERE (0!=(1))
When I click this one, I get the error.
The Object Matching lists work - I get the sidebar populating when I type a summary into a new incident.
When I went in to the incidentLayout.ServiceDesk form view, I couldn't click "Edit Matching Settings". I unchecked "Enable Matching Panel" and saved. When I re-selected it, I got this window:
But I don't know what the settings should be (I couldn't open it before).
Is it working for FRS_Knowledge?
Do you know if it has worked before? If so, did you customize it?
-> do you have a backup of the time it worked?
Since there are a lot of settings and you hopefully are in a test environment, you can try to
- manually add some Basic object matching rules, e.g.:
- restore the default matching (this is the default from 2016.1):
Thanks, I'll do that.
Yes, this is on my development server, not live, but Live has the same initial symptoms.
But it is working again, with the same error message when I try to open it from Object Matching Lists.
And yes, It works for FRS_Knowledge
1 of 1 people found this helpful
- Run a metadata check once and see if there are some errors related to the Incident table.
- Please also run the query and check if there are duplicate entries (same name):
SELECT Name , DisplayName, Definition FROM Frs_def_object_matching WHERE (0!=(1))
- if you're lucky, you will find something related to this issue in the AppServer.frslog file.
Open up an Incident directly with HEAT Software if this doesn't help you.
They should be able to easily determine the root cause.
That query did return problems with Incident ObjectMatching. I have opened a call with HEAT support.
Thank you again for your assistance.
Working with HEAT support, I deleted the list, and recreated it back to the OOB settings from the Layout properties.