6 replies to this topic

[Nexim]

Is anyone else having problems with Saved Searches? I've tried searching the forums but haven't found anything so far.

I created a number of saved searches on the Windows client, which work perfectly. They sync down to my iPhone and iPad, but there are 3 or 4 of them that don't show any notes at all. Looking at the same searches on the PC, they contain numerous notes. The notes themselves have synced to my device with the correct tags, but the saved searches aren't picking them up.

Any ideas? I'm trying to incorporate Evernote in to my workflow and this is a show stopper!

[GrumpyMonkey]

Is anyone else having problems with Saved Searches? I've tried searching the forums but haven't found anything so far.

I created a number of saved searches on the Windows client, which work perfectly. They sync down to my iPhone and iPad, but there are 3 or 4 of them that don't show any notes at all. Looking at the same searches on the PC, they contain numerous notes. The notes themselves have synced to my device with the correct tags, but the saved searches aren't picking them up.

Any ideas? I'm trying to incorporate Evernote in to my workflow and this is a show stopper!

Hello. Welcome to the forums! I use saved searches every day on the iPad, and I have not had any problems. I think Evernote is working fine (at least, with my searches), so let's break down your workflow and try to find the problem. Could you tell us one of your saved searches (if possible, copy/paste word for word)?

[Nexim]

Thank you!

One of my saved searches, "Home ToDo List" is defined as 'tag:todo intitle:QHome -tag:done'. On the PC version, this brings back 2 notes. On my iPhone/iPad it says no notes found, yet the two notes have definitely been synced.

[GrumpyMonkey]

Hi. I don't see any obvious reason why that search wouldn't work. When I perform a simliar search on my iPad, there is no problem.

tag:en-api intitle:Evernote -tag:test

I have 28 notes in teh en-api tag, 27 of which have "Evernote" in the title, and only one of which has the "test" tag, so I got 26 hits on a search, as expected. I can at least confirm that the search grammar is working fine for me.

So, I think at this point I would recommend you simplify everything to see where things are breaking down. Make two notes called "alpha evernote" and "beta evernote" (lower-case). Then, create two tags: "two" and "one" (again, lower-case). Alpha gets both tags (two and one) and beta gets one tag (one). Your search on the Windows machine should only return one note (beta). The same thing should happen on the iPad. Let's make sure that this works.

tag:one intitle:evernote -tag:two

The search worked fine for me on my iPad just now.

[Nexim]

Ah, I literally just figured it out.

The title of my notes was "QHome: blah blah". By taking out the colon, thus making it "QHome blah blah" it works perfectly. It looks like the intitle parameter on the iPhone/iPad clients is a bit more strict than the desktop counterparts.

The solution for now is just to take out the colons, or add them to my search parameters.

Thank you for your help! Is there any where I can report this as a bug officially?

[GrumpyMonkey]

Ah, I literally just figured it out.

The title of my notes was "QHome: blah blah". By taking out the colon, thus making it "QHome blah blah" it works perfectly. It looks like the intitle parameter on the iPhone/iPad clients is a bit more strict than the desktop counterparts.

The solution for now is just to take out the colons, or add them to my search parameters.

Thank you for your help! Is there any where I can report this as a bug officially?

Glad to hear you got it figured out! I am not sure if it is a bug or not, but you can report it to support (see my signature).

The reason I was recommending you simplify the test case is precisely because different clients are working in different ways with the API, and it isn't always clear what is happening on each client, so a capital letter here, or a colon there might throw things off, and diagnosing the problem is sometimes difficult.

For example, many (now all?) of the clients have been adding an asterisk to the end of simple search terms (not searches using attributes, though) automatically. Android (and I think the Web as well) will display the asterisk in the search, so that you know what the filter is, but the iPad will not, and you sometimes have to guess.

In general, the Evernote search works well, but as you begin using more advanced search grammar across several clients you encounter inconsistencies. On the forums we are trying to keep track of these to help the developers iron them out. I've started one thread about this at http://discussion.ev...ms/#entry123953

[Nexim]

Ah, I literally just figured it out.

The title of my notes was "QHome: blah blah". By taking out the colon, thus making it "QHome blah blah" it works perfectly. It looks like the intitle parameter on the iPhone/iPad clients is a bit more strict than the desktop counterparts.

The solution for now is just to take out the colons, or add them to my search parameters.

Thank you for your help! Is there any where I can report this as a bug officially?

Glad to hear you got it figured out! I am not sure if it is a bug or not, but you can report it to support (see my signature).

The reason I was recommending you simplify the test case is precisely because different clients are working in different ways with the API, and it isn't always clear what is happening on each client, so a capital letter here, or a colon there might throw things off, and diagnosing the problem is sometimes difficult.

For example, many (now all?) of the clients have been adding an asterisk to the end of simple search terms (not searches using attributes, though) automatically. Android (and I think the Web as well) will display the asterisk in the search, so that you know what the filter is, but the iPad will not, and you sometimes have to guess.

In general, the Evernote search works well, but as you begin using more advanced search grammar across several clients you encounter inconsistencies. On the forums we are trying to keep track of these to help the developers iron them out. I've started one thread about this at http://discussion.ev...ms/#entry123953

Yeah, there are obviously a few different interpretations as to how it should operate which I hadn't realised before. I'll add this to the thread that you created and hopefully it's something the developers can address in time.

Thanks again for your help