If i use a portal and attach a button to it ( place the button iside the portal) it would be nice if it would be able to execute (on action) related methods of the portal and not only the methods of the current form.
Currently i have to create a “trigger” script for those methods since i do not want a global method for this..
Rainer
use a tabpanel instead!
If i want to use a tabpanel i would do so. But i do not want to.
Using a tabpanel does not solve the problem. It is a workaround..
Tabpanels are not a workaround for this. Tabpanels are meant for this. Have a look at how it is used in the CRM sample.
Why do you call it a workaround?
a button in a tabpanel launches exactly the method what you ment!
Can you explain why you don’t want to use a tabpanel?
But If i use three different forms where i want to display the data (or parts of it) from e.g. one main table XY, a Tabpanel solution would give me on all three froms the same layout and the same fields.
With a portal i can use just the related fields that i want to show up.
Another problem: What happens if i change the layout of a form used by a Tabpanel ? This would alter all TabPanels..
I see a lot more advantages of using portals than using tabpanels:
Flexible Layout
Changing the related form does not change displayed data on other forms
Exclude the fields i do not want
using different portals from the same form with different layouts
If you use for every ‘portal’ a special form(table locked-view) and bring them into a tabpanel (with taborientation: HIDE) than they behave the same as portals!
a tabpanel is much more flexible than a portal!
make a special form, with table-locked-view and bring it inside a tabpanel
set the taborientation on HIDE and you have your portal!
Now you can bring in your button, and execute a method on the related data!
If you use for every ‘portal’ a special form(table locked-view) and bring them into a tabpanel (with taborientation: HIDE) than they behave the same as portals!
a tabpanel is much more flexible than a portal!
make a special form, with table-locked-view and bring it inside a tabpanel
set the taborientation on HIDE and you have your portal!
Now you can bring in your button, and execute a method on the related data!
This would mean that i have to create 10 (!) new forms for 10 different Tabpanels, instead of using only 1 (!) form with portals.
IsnM-4t that stupid ? What if i need 100 different Tabpanels …
I did not say that a solution with tabpanels is not possible, but it makes 10x more work for the same result. ( → useless..) and is limited compared to a portal ( not in functionality, but in layout - due to creating a new form for each different layou)
BTW: I just asked for a way to execute related methods directly from a portal. e.g. buttons placed inside a portal field should not just be able to execute local methods- they should also be able to excute realted methods…
Rainer
what do you mean with related methods???
relations doen’t have methods.. Forms have methods..
and to give developers an option to choose ALL the methods they have, so not only local and global but all the methods of all forms is a big change and introduce many problems.
If you are saying just forms that are there through a relations, that doesn’t make any sense, because why those and not of the forms that can be ‘accessed’ through a relation? Because from a portal perspective there is no difference.. The method you call on doesn’t have the data you see in the portal anyway…