Portal - carrying over records to new layout

[lidocayne]

Hello! I'm hoping I can ask my question and it be clear what I'm going after.

I have a layout which contains a portal of various information. Each line of information could be considered similar to what you would see on an invoice (for sake of simplicity we will say it is an invoice).

What I am wanting is for there to be a button on each line of the portal. If the user clicks the button, it will take the user to a new layout (this part is obvious and easy to do). However, I also want that portal's line information to also be carried over to the new layout. THIS is where I am having problems. How do I get the line they clicked on to be carried over to the new layout?

Thank you! and I hope I'm [somewhat] clear on my question!

[comment]

If you mean go to another layout to view the details of the line item, then use the Go to Related Record [] script step.

[lidocayne]

@comment:

Thank you! It's closer, but here's the issue I'm having with the Go to Related Records [] - when I am asked which layout I want to use, the layout I want to display it in isn't an option. Why would that be the case?

If I go in and make a copy of the layout I want to use and change the show records from field to the same table that the portal is from, it works.. HOWEVER other fields on the form don't work then. I look at my relationship diagrams and the tables are all connected using pK/fK so not sure why the layout I want to use isn't working.

Thanks!

Edited October 28, 2010 by Guest

[comment]

the layout I want to display it in isn't an option. Why would that be the case?

Hard to tell from here. To continue your invoice example, you would go to related record from LineItems, using a layout of the LineItems table. Assuming that Invoices and LineItems are related (by InvoiceID) there shouldn't be a problem - unless you want to display the record in a layout of another table, which of course isn't possible.

[lidocayne]

I am attaching a basic outline of the dB that I am creating. On the summary screen layout, the epap column in the portal is a button. If you click that, it does the whole Go To Related Records thing, yet it won't carry over the EPAP (in large print) on the DME order form. It just seems to retain the first value (e.g. you click on the 18 of record 1, and it brings over the 1st value (12) not the 18. Any idea? Do I have my relationships set up wrong?

Thank you for all your help everyone!

Edited October 28, 2010 by Guest

[comment]

I don't really understand your tables and relationships, but this is NOT like an invoice. In an invoicing solution you have:

Invoices -< LineItems >- Products

and you have:

ptDemographics -< papRxLine >- papRx -< orderForm

and you go from papRxLine to related record in ptDemographics, which doesn't make sense (the parent ptDemographics record already IS the current record). And your layout named "DME Order Form" is set to show records from ptDemographics??!

[lidocayne]

Thanks for the reply comment. So if I was setting this up similar to a invoice, then I guess it should be more like:

ptDemographics -< orderForm -< papRxLine >- papRx

The products equivalent in my setup would be the papRx ... the line items is the papRxLine, and the order form would be similar to the invoices I suppose. It's that last (orderForm = invoices) where I'm a bit shaky... but it seems like that's where my issue lies, would you agree?

EDIT: Starting over... I see the issues that are coming up and fortunately I'm early in the development process that I can do this.

Edited October 28, 2010 by Guest

[comment]

it seems like that's where my issue lies, would you agree?

I cannot answer that without knowing what your tables represent in real life.