04-18-2019 12:53 PM
Hello everyone,
I'm not sure if this is possible but the scenario we're facing is that we have many external autofill keyword sets to help users when indexing. Recently we've seen documents incorrectly indexed because someone will type in a primary keyword that is incorrect for the document but is a valid keyword value and does populate the related keywords. The problem we're seeing is that someone will recognize their mistake and then type in another primary key, except this time it's an invalid primary key. No data is returned for that primary key but the previous data, populated with the previous incorrect but valid primary key, is still there.
I was hoping we could build some logic in the SQL query of the autofill to return blanks in the related keywords if the primary key is invalid, but so far am getting errors any time I try to add an IF/Else or CASE statement to the query in Config (works in SQL server).
Has anyone had a similar issue and/or had any luck with adding conditional logic to SQL queries in external autofill keyword sets?
11-26-2019 05:43 PM
Yes sir - that's the tricky bit. Nicely done.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.