Page 1 of 1
Template Bids
Posted:
Fri Nov 05, 2010 8:04 amby maidanss
Hello All,
Complete 2.2
FMPA11v2
I have a situation which calls for having a set of template bids which would be visible to all the available projects through a constant portal besides the current “ProjectBidsâ€
Posted:
Sat Nov 06, 2010 4:01 pmby John Sindelar
Sure. It's just some scripting. You could even modify the relationship to Bids so that it showed both this project's bids and the "all" bids. The use portal filtering to restrict our current bigs portal to just this project's bids. Now copy and paste this portal on to another tab (or somewhere else) and change the portal filtering to show just these all bids (bids where there is no project id).
Nice thing about doing it this way is that since both kinds of bids are in the same table our routine for turning the selected bid into an invoice will work on both kinds of bids.
Hope that helps,
John
Posted:
Sat Nov 06, 2010 10:01 pmby maidanss
Thank you John,
Your suggestion worked like a charm. It was so simple, yet so effective. I just changed the relationship from "=" to "x", added a new portal, made the filter for the original portal and walla everything fell in place.
Thanks again & Regards
Posted:
Sun Nov 07, 2010 8:57 amby John Sindelar
Nicely done.
The only thing I'd suggest is that your "x" relationship means that you'll be running that filter calc on *every* bid every time. As you get more bids it will be faster to have the relationship show only the current job's bids plus the bids for "all" jobs, and then filter the portals as you're doing now. That runs the filter calc on just the smaller set of bids which the relationship presents.
Posted:
Sun Nov 07, 2010 3:16 pmby maidanss
Sorry John, I am not following your drift there, what do you suggest I use instead of the "x".
Thanks
Posted:
Sun Nov 07, 2010 4:33 pmby John Sindelar
Create a relationship that shows all bids for the current job, plus all the "always show" bids. For these "always" bids, give them a project ID (_id_Project in the bids table) like "always" and then create a new calc field in the project table, something like...
_id
& ¶ &
"always"
...and link this to the _id_Project field in bids. This way the relationships is true for substantially fewer than all projects and your filtered portals have to do less work.
=)