Subject: RE: Getting Callhandler Template fails Replied by: David Wanagel on 15-02-2010 06:40:46 PM The error is correct: all query columns must be indexed or boolean: column=DisplayName We put a restriction on what filters can be applied as some filters would can internal database performance issues. Unfortunately, the display name column is not indexed on call handler templates. I've sent an internal email to the data team to see if we can get that field indexed, but it won't help for current releases. Complete error response pasted below: <ErrorDetails> <errors> <code>INVALID_PARAMETER</code> <message> all query columns must be indexed or boolean: column=DisplayName </message> </errors> </ErrorDetails> This document was generated from CDN thread
Subject: RE: Getting Callhandler Template fails Replied by: Shadan Saniepour Esfahani on 15-02-2010 07:21:38 PM Thanks for the reply! So what are the columns that are indexed for CallHandler templates? Best regards Shadan
Subject: RE: Getting Callhandler Template fails Replied by: David Wanagel on 15-02-2010 07:40:11 PM It appears that the only columns indexed on call handler templates are: ObjectId, FileName and AfterMessageActionObjectId. Internally it looks like there is an agreement that we can index the DisplayName column as well, but it won't help for current releases. -Dave
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
