Travis_Schwartz

ah... I apologize for the misunderstanding—I didn't look closely enough to realize it was different. Do I need to tell it what change I want it to make, or is it saying "a change happened in this constraint and we want to make that change fire"? Because even adding it isn't hiding the button. I gues...

I have the copyright in the production setting. I added to the codepen as well: https://codepen.io/tschwartz-arrowhead/pen/WNgWwRE I'm not sure what I was doing with that line 10. I've gone back to the drawing board on this.I started with updating the CSS on the form to be: .mktoForm[data-form-sub...

I got it to hide the submit button, but now I can't get it to show on active = true: https://codepen.io/tschwartz-arrowhead/pen/WNgWwRE My guess is that it has to do with the order of the functions in the JS... I'm not just sure if that's the case, and what to do to fix it.

@SanfordWhitemanSo I feel lIke I'm super close and there are just some minor things I would like to clean up to wrap this up.Here is what my form looks like right now in web personalization:  What I would like to do is1. Make the APPLY button not visible (not just greyed out) till the "Let's get st...

haha it's always rewarding when you figure it out. I am having some challenges with styling the button. I'm using it inside of web personalization and it seems to be pulling the CSS from the template and I'm not able to figure out how to override it.

ah... for anyone following this... case matters... haha my field name needed to be Active, not active.

I noticed I didn't get the button element correct and was using a class instead of an ID for this section:

I've updated my button with that and am now no longer receiving the error message, but am still unable to generate the other fields. Another difference I noted was that your field for the secti...

I wasn't getting it to work, so I went back to square one and tried to follow your example but I'm still not getting it to work. I'm probably missing something trivial, but JS is not my strong suit. Here is what the form looks like in the editor:And I've set up the visibility rules to change when ac...

ok... I've gotten to where I'm stuck. This is what I've got: I'm guessing that I need to use API to change the visibility value which will then impact my visibility rules? Also, would I be using API to control the visibility of the CONFIRM button?