Quick Filter not searching, posted by Alan Grant on Wed Aug 10 15:40:49 2016
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching? |
Quick Filter not searching on Enter, posted by Alan Grant on Wed Aug 10 16:46:09 2016
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching? |
Re: Quick Filter not searching on Enter, posted by Alan Grant on Thu Aug 11 16:22:26 2016
|
Yes it works fine in this forum. Interesting that when I open my problem instance from latest Chrome it works fine but not IE 11. I'll dig into browser settings and post back when I have more info.
| Andreas Luedeke wrote: |
|
I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does it work for you with this logbook?
| Alan Grant wrote: |
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?
|
|
|
|
Re: Quick Filter not searching on Enter, posted by Alan Grant on Thu Aug 11 16:40:47 2016
|
Yes it works fine in this forum. I also discovered my problem is resolved using Chrome. I'll dig into browser and let you know when I find something.
| Andreas Luedeke wrote: |
|
I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does it work for you with this logbook?
| Alan Grant wrote: |
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?
|
|
|
|
Re: Quick Filter not searching on Enter, posted by Alan Grant on Thu Aug 11 17:09:47 2016
|
Found the problem. I needed to turn on Compatibility View in IE for the site. Regards.
| Alan Grant wrote: |
|
Yes it works fine in this forum. I also discovered my problem is resolved using Chrome. I'll dig into browser and let you know when I find something.
| Andreas Luedeke wrote: |
|
I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does it work for you with this logbook?
| Alan Grant wrote: |
|
With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?
|
|
|
|
|
Datetime format with elog client, posted by Alan Grant on Wed Oct 26 16:39:38 2016
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
Re: Datetime format with elog client, posted by Alan Grant on Wed Oct 26 21:41:42 2016
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
Re: Datetime format with elog client, posted by Alan Grant on Thu Oct 27 04:16:10 2016
|
I really appreciate your reply David.
There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating? It sounds interesting.
The only thing I gather right now from what you're saying is that there's essentially two locations where a field can be defined - in the Config file, or via the format of the data itself in the client command - but I could be wrong.
| David Pilgram wrote: |
|
Hi Alan,
I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately. Define one, and the other is defined.
I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others. I can understand that, and made a different solution to what I wanted to do.
| Alan Grant wrote: |
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.
I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.
| Alan Grant wrote: |
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.
|
|
|
|