Hi Ben,

Thanks for the zip file, the new dlls fixed the exception problem, but I still have some issues with the datetime range feature.

Notice in the 1st picture that I did a Search without selecting the CallDateTime fields and returned 3 records, one with today's date.

Now noticed in the 2nd picture that when I select the CallDateTime fields, I don't get any record, even thought there is a record with today's date.

Edhy Rijo

Looks like when we added the functionality for the Searching event, we didn't take into consideration the fact that more than one of each field might make it into the list.  Here are the DLLs for the fix.

Hehe, nope, I just looked right past it... sorry.

Hi Ben,

I posted the stack trace in the original message from the red exception dialog 

Do you need something else?

Edhy Rijo

Well, you should be able to use the same field twice.  Could you post the stack trace for the error that you're receiving (maybe from the red exception dialog that you get).  Sounds like it's a Dictionary<TKey,TItem> issue, but I'm not sure where it might be coming from.

Hi,

I have a Browser Dialog in which I need to search on a DateTime field (using the date portion only) using a range condition >= and <=.  I added the same field CallDateTime twice with the >= and <= condition (see attached image), and when doing the search I got the following error:

As I understand, this error may be generated by adding the field twice in the browser dialog, so if this is the case, how can I handle a search on the CallDateTime field using a range date for the same field?

Edhy Rijo