Here is what I want to do. I want to search in article. With text string "XXXX" and then a number in the same line "22663" and the search result would be listed according to ascending order of the "22663" that it has found.
For example I want to search "highest year" human lived ever. So there should be a number in the same line or near the line. And I want the results would be based on ascending order of the year.
Thinking about Google's Custom Search API (or Web Search API) to search for keyword, then saving the first couple thousand results, and then searching through each file with the above process.
Related
I'm trying to find a resource or explanation for how to determine how a field will display in the criteria or results dropdown of a saved search. For instance, in the results I would like to see the PO# field (fieldId:otherrefnum). But when looking through the drop down, I see neither of these as options. This has been a serious source of frustration for me with many other fields, I'd like to find a definitive way to avoid wasting time on this in the future.
Thank you!
There are a number of contributing factors to this.
The field names you see on forms may have been re-labeled by form customizations
Netsuite normalizes transaction searches to which leads to some (IMO) odd column name re-use.
A lot of old fields or fields tied to functionality (e.g. transaction status fields) don't follow the regular pattern of numeric id and text name.
The records browser helps quite a bit. You can search here and see that otherrefnum is named 'PO/Check Number' in the search editor. (An example of field name normalizing referred to above)
If you look at transaction you'll see it is just search filters and columns. If you compare to Sales Order you'll see something perhaps more familiar in terms of fields.
Even armed with the records browser experience is still needed. e.g.
A sales order has an items sublist and one of its fields is itemtype. In order to get that value in a search you need to select Item fields and then choose Type. A Sales Order's items.description column becomes the line level memo field in search results.
Hope this helps
the product search doesn't seem to work as expected. Products are obviously supposed to be searchable by their product number according to the search settings in the backend. But when I search by product number there are no results. I tried to set the ranking to a higher number than 1000, but also no success.
A possible workaround would be to add a product number to the search keyword field, which actually works. But this is not really a good solution considering that the shop contains thousands of products.
Is there something I might have missed in the system settings? Or does the search function probably have a problem with product numbers with dashes (example: 99-670-846-0)?
Thanks in advance!
I am using a Microsoft DB application (AXAPTA) that lets us search various fields by typing criteria at the tops of the table. An example would be to filter item numbers to those starting with a 2 by typing 2* or excluding items with bell in the description by typing !bell. Quotes are not normally needed. We often combine multiple criteria by separating them with a "," For example, 2*,9* where the "," acts as an OR. Unfortunately, I cannot figure out how to create a multiple criteria AND. What I am trying to do is exclude items that have DNU in the description AND also have bell in the description.
My thought would be
!DNU & bell
but that doesn't work. Any ideas? I am sure this is simple, but I am stuck.
You need to use the advanced SQL query syntax, which can also be put in the filter location.
You'll have to play with it a while to get exactly what you want, but see these links below. You'll probably need to use a combination of info from the different links:
https://technet.microsoft.com/en-us/library/aa569937.aspx
http://www.axaptapedia.com/Expressions_in_query_ranges
https://msdn.microsoft.com/en-us/library/aa893981.aspx
https://learn.microsoft.com/en-us/dynamics365/unified-operations/fin-and-ops/get-started/advanced-filtering-query-options
I have a table with a lot of data. One field is a string for example
searchableField
row 1: abcdefgdefg1hijklmnopqrstuvw234234
row 2: abcdefgdefg1hijklmnopqrstuvw2dsfds33
row 3: abcdefgdefg1hijklmnopqrstuvw234234
row 4:
abcdefgdefg1hijklmnopqrstuvwweewere333wr
row 5:
abcdefgdefg2hijklmnopqrstuvw234222aadfff
row 6:
abcdefgdefg1hijklmnopqrstuvwdsfdsf
I only want result row 5 back, but adding search therm defg2 won't work.
In some other cases I want onl y result 1, 2, 3, 4, 6 back. but also searching on defg1 won't work for me.
Something that should work for me is a filter, but unfortunately there are no filters with contains. What can I do as work around?
Please read the How full text search works in Azure Search article. It will help you understand how your documents and query terms are processed and how to customize the behavior of your search index to achieve the results you want.
In your case, you might want to create a custom analyzer that will break up the long terms in your document into smaller ones that are likely to be used as query terms by users of your application.
Alternatively, you can issue a wildcard or a regex query using the Lucene query language to simulate the contains behavior you're looking for. More information here: Azure search, search by partial terms
Below lucene query will help for doing a like or contains search as above question
item : /.* defg2 .*/
you can use search.ismatch or search.ismatchscoring functions
ex:
"filter": "search.in(metadata_library, 'a3e9838f-3fec-49d8-a1ea-46f361238ffd') and search.ismatch('[exe pixel!][test new tags 102][css monitor]', 'metadata_tags','simple','all')",
I need to find the number (not necessarily the tweets themselves) of Tweets that have been posted on a specific date for a specific search word.
So, assuming I search for "programming" and want the number of tweets for today, I'd like a simple number like "25". It would also be okay to get all the Tweets, then I could count them themselves.
But I can't seem to find a way to limit the resulting data of the twitter search api to a specific date?! Yet it must be possible, because the people from http://trendistic.indextank.com/programming/_24-hours do it too?!
Okay, colleague found the answer: just ad "since:yyyy-mm-dd until:yyyy-mm-dd" to the search query and you get only the tweets in that range.