griffigr

I know your pain! Have you considered setting an action via Pardot automations to change lead scoring values in SF? Might be worth checking out.

Pardot’s form handling completely sucks. If you’re running in parallel with Salesforce, create a web-to-lead campaign in Salesforce, setup the Salesforce connector in Pardot and drag in the campaign/leads via an automation rule.

Ninja Forms 3 no longer users field ID’s. They use a a field/merge key. You’ll need to isolate the field key by selecting your field > Administration > Field Key

Example: {field:first_name_123456789}

Once you’ve found the field keys for all the fields you’re trying to map, you’ll need to do some trial and error. Not sure which format will work, as I haven’t tried this yet.

Try with brackets (example only, your field key will be different): {field:first_name_123456789}

Try without: field:first_name_123456789

The NinjaForms webhook plugin uses brackets. The 3rd Party forms plugin may not.

• This reply was modified 6 years, 6 months ago by griffigr.

Had the same issue. I created a web-to-lead campaign in Salesforce, set up the Pardot connector and then applied an automation rule to drag those leads into Pardot automatically. Pardot does some things right, but form handling isn’t one of them.

<script type=”text/javascript”>
$(“input.DateFrom”).datepicker({
minDate: 1
});
</script>

Oh, man. Seriously thought you were an employee. Didn’t even check your user type! Apologies! I’ve got a ticket in with Ninja Forms, so hopefully they can get to the bottom of it.

When did this logic change? Up until about a week ago, I was able to assign any value I desired to a particular field.

The 1:1 relationship is extremely heavy-handed, especially when considering the necessity to customize field values for CRM integrations.

Also, I’m not the only user that’s going to raise questions about the change. From a long tail perspective, this wasn’t a wise decision. Form data needs to be as liquid as possible to allow for customization and scalability. With this change, you’ve essentially limited the abilities of your product. Not good.

Bump. Still trying to get an answer on this plugin. The free alternative (3rd Party Services) works like a charm. Yours? Not so much…

I realize both of these discussions are odd uses-cases for the plugin.

Similar to the other discussion, I, too, am pushing each form to a unique POST URL. Plus, we’re using Ninja Forms and conditional fields. CF7 gives us much more control over field ID’s/names, whereas Ninja Forms assigns a unique ID to each field, thus forcing our hand in having to create a new “service” for each form. Thing is, CF7 doesn’t do conditional fields, so that’s not much of an option at the moment. Admittedly, it would solve this particular issue were it a valid option.

Any ideas as to my options? Appreciate the help and kudos on a great plugin.