Who Viewed the Topic
Haven't been on for a while. I have a question. Does anyone know how to create mutually exclusive buttons? I have 2 buttons/fields that have 2 different value list attached. I would like to be able to click on one of the buttons/field and to have the other buttons/field become inactive and visa versa and to then reset to both active in the next record so that I can then choose again.
If I click buttons/field (1) I want buttons/field (2) to be inactive and if I click buttons/field (2) then buttons/field (1) to be inactive but when I create a new record then both are available to choose again.
Please forgive me but I am still learning , I am sure a script would be required but I don't have that type of expertise and I have exhausted all the help files and can't find what I am after.
Any help would be much appreciated. This is a personal project (actually for my wife).
I would like to create a button that copies data from specific table and fields to other ones on display in my form. The context for this is that I am creating a button that copies data that has already been entered and displayed in some text merge fields. i.e., Account address (first table), and I would love to have that data copied to the location address fields (second table).
See attached file.
Any help would be gratefully received (Complete beginner).
DB_SC_Grab- button question.tiff
Apologies if this in the wrong place, but it seems like the best fit. Just wondering if anyone can help me out with a script I'm struggling with.
The background: I have a button I'm using to launch a new window with another layout, then create a new, related record. This action will only happen if the user has completed a specific field in the original layout (__pkCollectionRef), step one of the script.
With the new window open, the user will then make a selection from a checkbox set and close the window, which will put their selections into a field in the original layout.
This part's all fine. What I want then, however, is for the button to be made inactive once they've completed their selection, so the script won't run if they press it a second time (this is to prevent the creation of redundant records - there is another button that will allow them to edit their previous selections if required).
I've attached two screen grabs of the script steps. The first is the script I require help with, the second is the script run if the necessary conditions of the first are met (i.e the creation of a related record in a new window and layout).
The _fkPickList field in the original layout will only be populated upon the creation of the new related record, so I had thought that adding the isValid calculation as a means of halting the script would do the trick, however what's happening is that it's preventing the script from running in the first place.
As a side note, I've also added conditional formatting to the button so that when the _fkPickList field isValid the text is greyed out. This one discourages pressing the button a second time, however, not prevent it from working.
Thanks in advance for the help. All comments appreciated.
I've gotten a lot out of this forum, so I try to pay it forward when I can, even though it'll likely only benefit newbies.
I have an "image" button that is tied to a popover. So you click the button, and you get the popover. Easy enough. Usual UI interaction is that if you click the button, the popover appears, and if you click it again, the popover disappears. Again, all typical FM stuff.
FM does not allow conditional formatting of image buttons to change the color. I wanted to emphasize to the user that for the layout field in question (in the popover), data has been entered. So I created another layout object -- an oval/circle surrounding the image button -- that is displayed only if one or more of the fields of the popover tied to the image button has been populated. Again, typical FM stuff.
What was flummoxing me, though, was that the image button wasn't "working" as expected. If you clicked on the button, the popover appear. But if you clicked on it again, the popover would "re-appear," instead of disappearing.
The problem it turns out was that my oval/circle surrounding object was "over" the image button and in the foreground. So FM didn't see a user was still hovering over the image button, but rather was hovering over the oval/circle object when it was shown. Thefore, if you clicked on the image button again, FM thought (correctly) that the image button was not previously being hovered over, and dutifully showed the popover again.
Very, very easy fix -- in the layout edit mode, I simply moved the oval/circle object to be behind the image button. Everything now works as expected.
I hope this tip helps someone! It took my around 90 minutes to figure out what was going on . . . . . .