You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pulling down my results specified by the client, without using elastic search, is there an easy way to search results, outside of the .find method?
For example I find all my data and store it in @fmResults
If i search "23" it should return @fmResults[0] & @fmResults[1]
If I search "Jim" it should return @fmResults[1] & @fmResults[3]
I know I can build a form with all the fields and pass them to the RFM .find method, but that is going to involve multiple search fields for each field and I'd prefer to have a single field.
Thanks for any suggestions
The text was updated successfully, but these errors were encountered:
Several ways to create complex rfm searches with simple front-ends (a single-field search form).
An Rfm resultset is just an array, so you can use any ruby method that iterates over the array to filter specific records.
Use a single field on your search form, then programmatically build a compound rfm find request where the search criteria is inserted into multiple find-requests, with each request focusing on a specific field of your layout.
Create a calc field in Filemaker that concatenates the fields you want to search on, index that calc field, then perform your rfm query against that calc field.
Each of these have benefits & costs, and there are probably yet more ways to do this. These are just the ones that come to mind.
I'm pulling down my results specified by the client, without using elastic search, is there an easy way to search results, outside of the .find method?
For example I find all my data and store it in @fmResults
I know I can build a form with all the fields and pass them to the RFM .find method, but that is going to involve multiple search fields for each field and I'd prefer to have a single field.
Thanks for any suggestions
The text was updated successfully, but these errors were encountered: