Hello. I am looking for feedback or recommendations on how to implement this scenario:

A contract for a person could have up to 50 or so fields… a person could have 1 to 20 or so contracts………and I would like to implement a method to see the history of the previous contracts. So I was thinking portal, but a portal with 50 or so fields?

Your advice is greatly appreciated

Thanks in advance

Hi, typically in a portal you would show the most important fields, that help you to identify the record. Then, you place a button in the portal (which will show up for each line) which performs a Go To Related Record and brings you to a layout that has all the fields.

In other cases (although 50 fields is a bit much) the often overlooked "table view" (View/View as table) can be very useful to present a lot of data in a relatively smally space.

Regards,

Peter

Thanks that makes sense.

For the portal, when I am just showing 5 or so "meaningful" fields (and have the button that will jump to a layout with all the fields --in a table view), do I set the field as NOT being able to be populated via Behavior?

Basically I just want a portal to "display" these fields and the user can NOT change them or add lines or edit the existing lines.

Thanks

If you don't want to allow editing through the portal, yes, you would set the behaviour to disallow entry in browse mode. Then, if a user tries to enter a field, the entire portal row is selected in stead. You might want to keep entry in Find mode though (you can find related records through a portal !).

Regards,

Peter

.......you place a button in the portal (which will show up for each line) which performs a Go To Related Record and brings you to a layout that has all the fields. ........

Peter

I am having issues with the button in the portal. If I have 4 lines in the portal, do I put the button on each line? What if the line has no data on it-- won't a button look funny on a blank line?

Thanks in advance

For a button in a portal, put the button in the top line of the portal only, where the fields are. That will only show buttons for existing related records.

Hope that helps :

Thanks for the help, but I still am having difficulties. I put the button in the portal on the top line... and it shows for the existing records... but the line below as well. Once I start entering on the 2nd line, the button appears on the 3rd line (even with no data on the 3rd line).

I have attached the database that I am playing with to help me implement the portals. Once I get it working correctly, I will re-create in the live database.

Thanks for your assistance.

buttons-portal.zip

it does that because you are allowing records to be created through the portal (this option is in the Table Occurrence Relationship).

If you want to remove that, you can create a Calculation field to be a button:

Check out the attachment.

Does that do the trick for you?

Martha

multijob.fp7.zip

Works like a charm... thank you for all the help