Keyword Validation Based on Another Keyword Value - alternative to Cascading Data Set
We are looking to limit the values a user can select in a given keyword (Policy Number) based off a value they select in a different keyword (Account Number). In other words, we want the user to only be able to select policy numbers that are associated with the specific account they have already selected. As we understand it, this is exactly what a cascading data set does, however there is no way to systematically keep the data set current. The only option is to manually update the cascading data set in the configuration client. Is there a way to utilize an external validation on a keyword? How are others ensuring data integrity in this type of scenario?
