Conditional fields/buttons in Portals

[Digitalbrit]

Hi all - as part of my portal, I am using a calculated field to return either a value or a "blank".

What I want to achieve is to then assign a button(script) to that field in the portal, but for this to only be there when there is a value present i.e. if there is a value the hand cursor should appear and the button can be pressed, whereas "blank" doesn't result in the hand cursor nor the ability to press the button.

At the moment no matter if there is a value or not, the hand cursor is appearing and the button can be triggered. Clearly this is happening because the field is still there, its only the condition of the field that says whether something is shown or not.

I could detect in the script whether there is a value present in the field and respond accordingly, but I really want to avoid giving the impression that the button is there in the first place (when its a blank) i.e. no hand cursor.

Any bright ideas or examples on how this can be done?

Also, I am seeing peoples examples where button graphics are actually one of the fields in the table. What's the reason for doing this when you could just put the button graphic in the portal?

Cheers

Tim

[Digitalbrit]

Have found this which might be a help - still working through it

http://fmforums.com/forum/showtopic.php?tid/198234/post/303977/hl/visibility/fromsearch/1/#303977

[Digitalbrit]

Have also found

http://fmforums.com/forum/showtopic.php?tid/198297/post/304164/hl/portal+scroll/fromsearch/1/#304164

It seems a popular way to make buttons appear/disappear is the 1 record relationship technique, however I'm doing this in a Portal, will that work "in" Portal? Best I try ...

[aldipalo]

Take a look at this file and see if it helps you.

If you have any questions let us know.

Conditional_Portal_button.zip

Edited October 26, 2008 by Guest