Basic Portal Functionality

[T-Square]

I am trying to redesign a multifile solution so that all the layouts are stored in one core file.

At the core of the system are clients, payments, sites, and deliveries. Each client is assigned to a site, and has deliveries made to that site. Payments are linked both to the client and the individual deliveries. Currently, I have layouts and scripts in each of the files of the solution, but maintaining the solution at a distance makes this method problematic (to say the least), but I want to unify the interface in one menu file that will read and display data from all the rest of the files.

To start, I have a layout that has multiple clients summarized on it. In this new version, I am building it using a global join on a calculation of 1, to enable all people to be shown. On this layout, I want a repeating button that will navigate to a single client's information in full.

Right now, I have 2 problems:

1) the portal doesn't want to scroll; and

2) the button doesn't work when it is placed on the portal itself (it just doesn't run). The button works when it is elsewhere on the layout.

Any help is welcome.

David

[ernst]

Hi Sunfish,

Questions about your questions:

You do have the "Show Vertical Scrollbar" option turned on, i suppose ?

And about the button, what does it do ? Trigger a script ?

Ernst

[Fitch]

The upper left pixel of the button must be within the first line of the portal.

[T-Square]

In reply to both of you:

Yes, the display scrollbox is checked. Yes, the button triggers a script, although I have tried setting it just to go to another layout with the same results. And, yes, the button is fully contained within the single portal row.

[ernst]

And do you see the 'people' in your portal?

[T-Square]

Yes.

[ernst]

I could reproduce this behaviour with no records present / found in the current file.

Could that be it?

[T-Square]

No. I see data from the destination file.

[ernst]

>>No. I see data from the destination file.

Seeing data in the destination file still works with zero records in the source file and a global on the left side of the relation.

But to scroll, or have a button that works, you will need at least ONE record found in the source file. No matter if the relation uses a global on the left or a normal field.

[T-Square]

Oh. I get you. But, yes, there is a single record in the menu file.

[Ugo DI LUCA]

Hi,

I think you may investigate more about what Ernst suggested as this is a common problem with self relationship based on constant fields.

Try to show all records and see if you get something to work.

Usually, as I also work on this kind of interface, I always put a If is valid(relationship) step in my script, as to not be leading to a 0 record found, which lock the entire solution.

I really think that is what you're experiencing.