Anchoring/Freezing Header, Scroll Rest of Record

[bcolburn]

I am trying to freeze a certain portion of my record template so it stays in place while I scroll through the rest of the layout much like freezing columns/rows in Excel for convenient reference. In essence, I want to make sure I can still see things like the patient name/date of entry when I scroll down on the layout. Any suggestions?

[jdu98a]

Really the only ways to create that kind of functionality is to use either a List View layout or contain all the data that you want to scroll through in a different table and view it through a portal on your layout. The portal solution is probably more what you are needing. That design technique can get hairy but it's not impossible. In fact, in many cases containing record attributes (things like addresses, phone numbers, and emails) in a separate table is actually preferable.

[Vaughan]

Create a list view layout with header and body (and optionally footer). In list view the header remains at the top and the footer at the bottom of the screen. Just ensure that only one record is in the current found set.

[HALBURN]

Really the only ways to create that kind of functionality is to use either a List View layout or contain all the data that you want to scroll through in a different table and view it through a portal on your layout. The portal solution is probably more what you are needing. That design technique can get hairy but it's not impossible. In fact, in many cases containing record attributes (things like addresses, phone numbers, and emails) in a separate table is actually preferable.

 

I know that this is a pretty old thread but can someone please explain how the portal method that jdu98 could work? Let's say that I have a table with 100 fields and I want the user to be able to scroll down a single layout and fill them in (like they would on a web page). How does putting them in a portal gain you anything? You still need to increase the height of the portal to accommodate all of the fields, and if you do that isn't the header going to scroll the same as if you used any other object to extend the layout vertically?

[comment]

I know that this is a pretty old thread but can someone please explain how the portal method that jdu98 could work? Let's say that I have a table with 100 fields and I want the user to be able to scroll down a single layout and fill them in (like they would on a web page). How does putting them in a portal gain you anything? You still need to increase the height of the portal to accommodate all of the fields, and if you do that isn't the header going to scroll the same as if you used any other object to extend the layout vertically?

 

I believe the idea refers to multiple records, not multiple fields in a single record.