![]() This also works well in FileMaker Go where unintentional taps don’t accidentally set off an unintended process. After reviewing, Doug West offered up an idea by simply using a global variable to achieve the same effect.Įither method provides an intuitive user interface that allows a user to select an item in a list before taking action on it. This is not the only way to provide this button in a FileMaker Pro portal row functionality. Not ( GetLayoutObjectAttribute ( “portal” “hasFocus” ) and (Get ( ActivePortalRowNumber ) = myPortal::RECORDNUMBER ) )ĭownload the demo file and give it a whirl! Now using the function to GetLayoutObjectAttribute, I can dynamically show the button only with the portal row is active with this calculation: ![]() So, to set this up, I had to add a field in the related table as an unstored calculation Get ( RecordNumber ). In FileMaker 13, you can with the new FileMaker hide object feature. So, what if you could just display the edit button when that row was active. So then we typically put a visual button off to the side like an “edit” button, but the result can be unsightly seeing “edit” repeated a dozen times on the screen. But sometimes you don’t want a button across the entire row. It’s pretty commonplace to put a button over a FileMaker Pro portal row object to trigger an event related to that particular row. I just figured this out and thought it was cool enough to share with you. Ready to Play Hide and Seek with a Button in a FileMaker Pro Portal Row? WordPress Repair and Troubleshooting Services. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |