Hey guys,

 

I am working on a database with the following relationships (with "---" meaing one and "<" meaning many [there are other tables/relationships etc, but they shoudl be irrelevant for this issue]):

 

"Jobs" --- < "Invoices" ---< "Line Items" --- "Line Item Calculator"

 

I have a portal on the "Jobs" table showing "Line Items." What I am trying to do is have a button on each portal line that will go to that record in the "Line Item Calculator" table. The issue I am having is that when I use the "Go To Related Record" script step it shows all of the items associated to that job, rather than isolating that one line item record.

 

Im probably jumping ahead here, but I have deduced that it must be using either Job ID key field or Invoice ID key fields, neither of which are unique in the Line Items table, and I want to use the Line Item ID which is unique to find the related record. So, do I set a variable and perform a find based on the portal row I am looking for, or create a 2nd occurance of one of the tables, or...?

 

Also, if it matters, I have multiple tabs on the Jobs layout and will eventually have multiple portals on different tabs.

Write a script which first goes to the related Line Item (the one clicked in the portal), and from there to the related (as seen from the context of the original portal's TO) Line item Calculator record. A Job record doesn't have a one-to-one relationship with any Line Item Calculator record, so you need to establish the context that does (the Line Item record).

Sorry everyone, I figured it out. I wrote a script to open a new window and then go to related records. I didn't realize that was going to cause such issues, but now I know. I just simply had to change it to create a new window on the "go to related record" script step.