You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
@ryanjdew Hi , I was writing a custom algorithm as a part of smart mastering as per my requirement in javascript. I need to construct custom query something like you can see as the return statement bellow, I am using this signature for the function-
I am attaching the matching option I am using.
Now the issue is this query isnt working when I am calling sm-match API, I can see that log is being generated that I have written in the algorithm. Could you please help?
The text was updated successfully, but these errors were encountered:
Thanks for your answer, I have tried that as well but not getting the expected result. As you can see, this query should match any value for the field "registerName" but I am getting this result attached here when I am executing sm-match function with the match option that I have shared before. result.txt
It is not considering "registerName" as matched item.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@ryanjdew Hi , I was writing a custom algorithm as a part of smart mastering as per my requirement in javascript. I need to construct custom query something like you can see as the return statement bellow, I am using this signature for the function-
function findMatch(expandValues, expandXML, optionsXML) {
//custom logic
return cts.search(cts.jsonPropertyValueQuery("registerName", "*",("case-insensitive","wildcarded","lang=en"),6.0));
}
Test_matching_option.txt
I am attaching the matching option I am using.
Now the issue is this query isnt working when I am calling sm-match API, I can see that log is being generated that I have written in the algorithm. Could you please help?
The text was updated successfully, but these errors were encountered: