Unfortunately, that solution causes the following error when I attempt to create the new campaign: json.field.message_footer.state.invalid:Instance value does not match any String value. Valid options are: AL, AK, AZ, AR, AA, AE, AP, CA, CO, CT, DE, DC, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY. json.field.required.us.address.fields.missing:state and postal_code need to be set if country is set to US. So it looks like I would also need to change the Country, is that true? And if so to what do I change it? And then let's discuss whether what we are suggesting to do here makes logical sense... If the footer using the default address from the account, then the state is displayed using the 2 digit Postal Code. So why would we stray away from that when we pass a postal code in a custom footer structure? I would think a much better interface would allow me to pass in AL or ALABAMA, but not BAMA, and it would ignore character case in the validation giving the user the ability to display their footer address in all lowercase or all uppercase or any mix in between.
... View more