This is my situation, I have a table called "create parts" which holds a set of record of parts standarized with their info, I created a filter with a field which is related to this table by "type"

for example:

"inventory" type (pull down): plastics <----> "Create Parts" Type

That would display all the parts in the portal that has the "type" I select. I would like to add a smart filter (a global for example) that if I start typing it filters within the current portal.

for example:

type: computer parts

Will display: System board, LCD, Memory, CPU, Keyboard, Mouse, etc....

If after I select "computer parts" in type and it shows all these records i want to find quickly "keyboard", I would like to have a global that by just typing "k" it would show me only the records starting with "K" on the portal and so on, the more letters the more accurate the result is.

Is there anyway this can be done?

Thanks in advance.

Try a condition where =

GlobalField = Left ( PartName ; Length ( GlobalField ) )

you got me lost there, where should i place that condition?

Ahm... where portal filtering conditions go?

http://www.filemaker.com/11help/html/relational.11.21.html#1033103

It did not work, my relationship is the following:

2 tables: Inventory & Create Parts

inventory::type <---> create parts::type

in inventory, my "type" field is set as a drop down menu where the value list is based on the "create parts::type" values so that would give me a unique value for each different one.

When I select the "type" based on the value list I am being able to see the related records based on the "type" since they match.

I tried what you suggested me and it doesn't do anything, the formula based on what you told me would be something like:

Inventory::gtext1 = Left ( Create Parts::Description ; Length ( Inventory::gtext1 ) )

right?

It's not doing it for me

Does this work for you?

FilterLeft.zip

---

P.S. Note the script trigger attached to the global filter field.

works like a charm, the only thing I found I didn't like is that when I applied it to my solution since it has a lot of graphics the "Refresh Window" makes the screen blink and it is very noticeable...

My other option was to make in the "create parts" a new field called "filter" and list the parts with the "type + word by letter" for example:

for a "door" part

Plastic

PlasticD

PlasticDo

PlasticDoo

PlasticDoor

and have a trigger that when the global is modified it refreshes the field that will be connected to the "filter" field with "type + global"

I tested it and it works but I don't know if its the best option

There is another option - but you can't use the same relationship to create child records, and the filter will be applied only after exiting the global.

FilterLeft2.zip

It works but it has to exit the record in order to update the result in the portal instead of doing it instantly, i made an example of how I want it to work exactly as I expect but i dont know if the way I did it would be the best way in the long run.

anyway I don't thing the "child" table (on my situation) would exceed the 300 records.

filterexample.zip

That's more or less how you had to it before portal filtering became available. Except you would use a calculation field to "explode" the product name, and the relationship would use two matchfields instead of concatenating type and name.

Not sure what does a record in your parent table represent, though.

my parent table basically is my "Inventory Products" table, where all the products in our database created, my child table represents a "Create Parts" table, this table is more like a standarization table where it would have the default information about a product.

For example if a data entry person wants to create a systemboard the "create parts" table would have this info by deault:

*Product description

*Category

*sub Category

*Weight

*Cost Price

*Sale Price

once this information is transfer to the actual part the data entry person can do the modifications that need to be done like fixing the description of the product, fixing the weight, or the sale price, etc.

Again, this table only represents standard parts to be created quickly instead of typing each information manually.

I am afraid now you have lost me. I am not sure if it matters, I just found it strange that you can select a type - but that field is not a global.

i just made it like that, would work as a global too, doesn't really matter, but as a plain text field I could save which type the data entry person selected.

It does matter, because if it's for viewing only, the field needs to be global - otherwise the selection made by one user will apply to all other users.

OTOH, if the selection is supposed to actually assign the parent record to a type, then it makes no sense to use it as a matchfied to child.

you are right about the global field so it wouldn't apply to all the users, but the user will only go into that layout one time for the specific product created.

these are the steps i follow:

1) the user goes to a blank layout to enter a part number (i validate if the part number is already created or not)

2) if the part number has already been created, display it on the main view, otherwise create it and go to the Creation view where this portal will be located

3) after making the changes go back to the main view

the only way a person can go to the creation view is by creating a new part number though the process

OK, I have no idea what that means - but since it works for you and seems unrelated to the original question, I suggest we leave it at that.