This is merely for the UI ease of use. Whenever I use this field, I will use all the contents of the field. So when scripting it won't matter which instance is currently on screen. If you have a better method, that is just as easy to use, I am open to suggestions.
I don't understand your question. The value list is simply a way to control user input. If you are in a script you may want to reference the value list but, as you say, you are in a script, so you are in control of the input.
@PattyB and @Malcolm I understand that this is for the UI ease of use. The aspect I dislike is that a single field contains information for different 'data'. And for me it's a no no. All that simply means I prefer to have in this instance a field per set of values. But since all of these are services, that may make sense for the OP.
FileMaker offers many ways to implement checkboxes, this one I personally dislike. But that's just me.
@PattyB There are many differences between Pro and WD.
In this case, each instance of your field have no awareness of what was inserted in the other instance. So as you edit instance A, instance B starts from 0 when you start changing its content.
I do not know if this may work or not, but it could be that a button would bypass the awareness problem. Send in a parameter that you will use in a filtervalues against the field in the script. If the value is not there, append it to the list in the field, if the value is there, remove it with the appropriate string substitution (I believe the value may or may not have a carriage return after it, so watch out for subtleties like that). You can then wrap your each field instance in a button, each having its own parameter.
If that does not work, you may be forced to create 3 distinct fields and have another field doing a list (fieldA ; fieldB ; FieldC).
There are plenty of those type of nuances between the sibling products of the platform. One other differences to note, stacked objects will also give you trouble on web direct, specially if you have an object with a button UNDER something else (click-through behavior is not the same, period).
I hope this helps. Please let us know if you find something that works for you.
1 Like
It seem as though it should be a portal collecting many different bits of information but that's a different question.
PattyB seems to have bumped into a product issue with WebDirect.
Thank you for the replies everyone! Here's what I ended up doing:
I made three separate fields, Services_Maint, Services_Chem, & Services_Snow. I set the Services field to auto-enter List ( Services_Maint, etc... ). Because there was an option to select a Package, or customizable group of services, I had to include a script trigger on the Package field, which is a pop-up menu. Here's that script:
Basically what it does is Filter out which services in the package are Chemical, Maintenance, and Snow, and set the corresponding fields correctly. The Calc in the Set Field removes any carriage returns at the end due to FilterValues.
A portal may be the cleanest way to do this on the back-end, it would make selecting services harder and take longer, so for me anyway that wasn't really an option.
Again, thanks for your help!
1 Like