Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
3 years agoSearching for phone numbers
- I have phone numbers stored under a login item, under the field "Phone"
- Say the phone number is +1347xxxx1234
- When running a search, if I search for +1347 : the login item is returned (correctly)
- When running a search, if I search for 1234 : no results are returned
- If the phone number is under "Notes", searching for any part of the number, returns the result
Is this expected behavior? Am I missing a search operator for "contains", rather than "begins with"?
Thanks!
1Password Version: 8.6.0 (80600068, on BETA channel)
Extension Version: Not Provided
OS Version: mac OS 12.2.1
14 Replies
- 1P_Rob
1Password Team
Hey, @speedbird. I've just tested and it looks like you're correct, the filtering feature only works on certain things, basically what is displayed in the list view, rather than in the details on the right. While it does work with substrings, that's not going to help you if the data you're looking for is deeper inside the item.
I'm sorry for the confusion. We've been tracking requests for improvement here and I've added your vote. It sounds like there are some complexities to overcome, but I think we can get there with some dedicated effort.
ref: dev/core/core#9056
- Former Member
Thanks for your suggestions. Apologies, daft user here, not sure I'm using the workaround correctly.
- I'm on the latest beta version
- Please see attached a sample item
- I'm trying to do a lookup for "1234" to locate this item
- Using cmd+F:
- Searching for +1347 returns the item
- Searching for 1234 does not return the item
- Using opt + cmd + F:
- Searching for +1347 does not return the item
- Also, searching for 1234 does not return the item
Could you kindly let me know what I'm missing? Thanks.
- 1P_PeterG
Community Manager
Hi @speedbird, thank you for letting us know about this. viswiz mentioned that we've added a filter function in recent Betas - I'd agree this is the best way to approach your question right now. If you haven't yet, I'd recommend updating to the newest Beta and try the
opt + cmd + fkey combination. Does that help in this case?We are improving search as an ongoing project, and appreciate you letting us know about your use case so we can better understand how to help. I'll look forward to learning how the solution offered here works for you!
- viswizSuper Contributor
It's a known problem of the current search implementation. Currently it doesn't search for substrings. It was partly addressed by adding a filtering function that can be used additionaly to search - available with the beta of mid February,