REST API to search multiple possible parameters - spring-boot

I have an application that will have a front end that contains fields for a provider. One of the options is to be able to search for different providers. There can be up to 6 fields populated to search on or they can only submit one field for the search. For example, it can search on firstName, lastName, taxId or it can just search on lastName.
Can anyone steer me in the right direction on how to do this? I haven't been able to find any relevant tutorials for this specific problem. Any examples or links to this type of solution would be greatly appreciated. Thanks in advance.

isn't it become very complex for programmer to validate every possible combination what if there are 30 fields available then there will hundred's of combinations to validate. Is there any other solution for that.

Related

Finding current Query-ed field Siebel

I'd like to know if it's possible to retrieve the field that a user is querying on the applet ? Let's say on Contact List Applet, user queries the Name field. So, how can I retrieve the field that's being queried on ?
Hope everyone can share their thoughts on this. Many thanks !

How to replicate Who bot people search criteria?

Need help in implementing people/user search in the entire organization with a fuzzy search
Microsoft Graph API
People Search
https://graph.microsoft.com/v1.0/me/people/?$search="Mary"
Perform a fuzzy search but this is done only on people collection of the signed-in user
Which doesn't give a result based on the entire organization
Users Search
Doesn't support following ODATA Parameters
1.$Search https://graph.microsoft.com/v1.0/users?$search="Mary" is not supported
2.$filter doesn't support $filter=substring(displayName, 1) eq 'abc, xyz'
3.contains is also not supported $filter=contains(CompanyName,'Alfreds')
Seems your are trying to search user among your organization. But the way you tried is not supported.
If you want to search organization user you could try in following way
https://graph.microsoft.com/v1.0/users?$filter=startswith(displayName,'Kiron')
It will show all the name start with given value. See the screen shot
Please refer to this official docs

How to create a quick search in CRM that spans multiple entities with grouped conditions

We are a housing association with a large CRM system (2016 & SP1). We have a new requirement that requires our users to be able to search for people who are current (ie not previous) occupants or residents or who are not residents (eg contractors)
For this purpose, we need to search the Person entity which has a related Tenancy entity. Person has TenancyType field with possible (option set) values Occupant, Resident, Contractor. Tenancy has TenancyStatus field with possible (text) values Current and Previous.
We tried using the following filter criteria in the quick view on the Person entity:
thinking that it would return all people who are not previous residents. However we noticed that it would filter out contractors because contractors do not have related tenancy records.
We needed to change the criteria to return all contractors OR all residents and occupants with no previous tenancy. So we changed it to the following:
at which point we got stuck because we noticed that it was not possible to AND together the second and the third conditions as the third one is a related entity.
We are wondering what the best way is to achieve the above bearing in mind that we do not want a separate view for each condition, eg one for residents, one for none residents, etc.
Any help or suggestion is greatly appreciated.
It is not possible to do this with a single query.
Instead, you can use two queries. If you do not want to do that, then using reports (as suggested by Alex) or a BI-solution would be other possibilities.
Thanks to everyone here who spent time answering my question. The following describes the correct answer:
https://community.dynamics.com/crm/f/117/p/241352/666651#666651

How to create a help-form in FormsBuilder?

I am required to make a form which will contain important keywords and their description, with the possibility to search between the words. It is loaded from the Help menu and it is designed to give the users detailed help informations about other components. (Just like every application's Help menu)
I only used forms to query tables, and I was wondering, what is the correct way to achieve this? Does Oracle support any feature that would auto-generate a help-form based on my 'Help' inputs from Property Palettes? or do I have to manually write data into a canvas? if so, how can I search through it?
I considered creating a table and writing help informations in it, but I don't think that is the correct way.
Oracle Forms, unfortunately, does not give you programmatic access to values stored in property palettes, so your solution will need to be custom made.
Create a table, e.g. HELP_TOPICS (keyword, help_text), add a list item that contains all the keywords; when a user selects a keyword, query the table to find the help text, and set the value on a display-only text area item on the page.

Multiple routing field in elasticsearch

I am a newbie to elasticsearch. i need a clarification. i can understand how routing works, but I have a question.
Can i create routing for an document with multiple field. if yes, can i search the
data using single routing value. Can any on provide any example about it.
Imagine I have 5 fields: [username,id,age,dept,salary]. Now i need to create a routing value for this document. Can I do so using the username and id field?
Thanks in advance.
In answer to your question: no, you can't automatically use multiple fields for a routing value when indexing a document. You can choose one and only one field, and that field must contain a single value.
However, you could manually concatenate the username and id field and pass it in the indexing request:
PUT /index/type/id?routing=username_id
{ body }
That said, routing is a feature for more advanced users. It is very useful but does make life more complicated. You say that you're a newbie, so I'd suggest not playing with routing just yet. That can follow when you're running a 50 node cluster.

Resources