Update Company Size/Employee Range forms | Community
Skip to main content
Hassina_Obaidy
New Participant
June 30, 2020
Solved

Update Company Size/Employee Range forms

  • June 30, 2020
  • 1 reply
  • 3914 views

We have a ton of forms on our website. We want to update the company range drop down field on the form. How do I make the mass update to all of the forms?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amy_Goldfine

This is a great opportunity to move to Global Forms, it makes it super easy to make changes like this! I discuss the advantages (and caveats) of Global Forms in my recent CHIMUG talk starting around 6:20 https://mugs.marketo.com/events/details/marketo-chicago-mug-presents-spring-cleaning-webinar-series-dry-clean-your-marketo-instance/

1 reply

SanfordWhiteman
New Participant
June 30, 2020

I assume you mean Number of Employees (SOAP API/Forms API name NumberOfEmployees).

 

There are 2 ways to make such changes:

 

(1) A true, permanent change to the Marketo form descriptor using  the Asset API for Forms. It takes some learning.

 

(2) A temporary change to the availble <option>s using JavaScript. In this particular case, Marketo will allow you to make direct changes to the DOM without any problems. You just need to wait for MktoForms2.whenReady() and modify the select.

 

In general, the cumbersome nature of such changes is why having only a few shared/global forms is recommended, not a profusion of individual forms.

Hassina_Obaidy
New Participant
July 6, 2020

Hello, thank you for your message. To clarify, if i wanted to change the values of employee range field on all forms globally, I'd have to access the API and go through the backend? 

SanfordWhiteman
New Participant
July 6, 2020

Hello, thank you for your message. To clarify, if i wanted to change the values of employee range field on all forms globally, I'd have to access the API and go through the backend? 


You only need the REST API if you want the change to be permanent so that the plain form embed can be used in the future, without any custom JS.

 

If it's not necessary to make that permanent change, you can do the same customization on the client side, on-the-fly.  For example, I was just rolling out a form where the dropdown lists come from {{my.tokens}}, rather than being stored permanently in the form descriptor.