Portal Filter

[no1tmorrow]

I have read post after post prior to posting this so hopefully I can prevent from being flamed.

I have a portal setup to display sub items. It works great. Now I am trying to filter out all the rows that have a quantity (field quantity) of zero. I tried a table with the field in it and then set a relationship to my portal records quantity but it does not do anything.

I also tried putting a field in the related (parent) table and then putting it in the relationship. Well it works except it will only allow me you enter in the portal quantity field the value that is in the parent record (I am sure that has to do with the relationship forcing the value) Does anyone know how to accomplish this?

Thanks

Thom

[mr_vodka]

Create a global field in the parent. You will want to change the relationship so that it is joined on your orig keys and also keyed from this new global field to your qty field in the child table occurence. Use the does not equal operator for this second criteria.

Now, if you set that field with the value of 0 it should display all records that do not have the value of 0 in the qty field. Make sure that the qty field is indexed. You can either script it so that the user can choose to either set the field or not to, or you can have it preset with the value if you wish.

[no1tmorrow]

Hmm. Just tried that and it forced the quantity field to be whatever was in the global field. I am attaching my project to see if that helps. It is the bidalternate layout that I am having a problem with.

Thanks again.

Thom

Bid.zip

[mr_vodka]

Change it to ≠

[no1tmorrow]

I don't think I can do that since I am wanting two results one that shows quantity of zero's and one that does not: so if I put ≠ (and set the global to 0) then that will work for hiding zero's but there is nothing I can put in there that will show everything. Maybe I am wrong.

Thanks again I truly appreciate it.

Thom

[comment]

Once a relationship is filtered, it stays filtered. So you can either have two relationships, one filtered and one not, and switch between the two portals using tab panels - or filter the relationship by

Parent::gMinimum < Child::Value

To hide zero values from the portal, set gMinimum to zero. To show them, set it to -1 (or lower, if you expect negative values).

[no1tmorrow]

comment,

Where do I put the Parent::gMinimum < Child::Value at?

Thanks

Thom

[comment]

In the relationship's definition. You already have this in your file, just change the ≤ to < and use 0 and -1 values to toggle between the two states.

[no1tmorrow]

Ok So here is the results

If I use < instead of <= then I can no longer create records in that table (portal)

If I use <= then I can add records but it forces the quantity I put in to be the quantity of the global field value that it is joined to on the parent table.

This should not be this hard (I wouldn't think anyway)

Thanks again

Thom

[mr_vodka]

I think it might make sense for you to either:

1. Script the adding of new record. Personally, I dont like entering data directly in a portal. Just my humble opinion.

2. As Michael stated, use two tabs. One for unfiltered, using a normal equijoin = and the other Filtered one using the method as described above.

[comment]

Well, assuming quantity is a positive integer, you could use the value of 0.5 with the ≤ operator to filter out the zeros. But filtered portals are really not suitable for creating new records.