Wordpress CRM Integration

Connecting Wordpress to your CRM easily and effectively

by

Ninja Forms Salesforce New Release v3.0.6

The Ninja Forms Salesforce CRM extension has a new release out – version 3.0.6.  It includes a few formatting changes that allow you to send a wider selection of characters through your form.  In addition,those of you with large forms will notice a major improvement next time you edit your form.

The Challenge

I discovered that people using larger Salesforce objects and larger forms were stalling during saving. Thanks to your support tickets describing what you were seeing, I could easily find and make the improvement.

When I first wrote the Salesforce extension, I didn’t imagine how impressive some people’s integrations would be – more than just adding a new lead.  Multiple page forms that create contacts, accounts, resumes, and campaigns, to name a few.  All those modules started slowing things down, considering that Salesforce has hundreds of fields available.

The Fix

I found how to improve performance without sacrificing any of the features, and the results are what you’ll experience once you upload to v3.0.6.  In this version, whenever you save your form, the plugin will clear out the list of fields you aren’t using.  This simple step helps immensely and several customers have tried it out and reported back successfully.

Thanks so much to those of you who took the time to report the problem you saw and explained it in detail.  It helped me make improvements for a robust product I hope you can use for years to come.

by

Capsule’s New API v2

Capsule has released their new API v2 and they will be dropping v1 in January.  So what does that mean for you users of the Ninja Forms Capsule extension?  Hopefully nothing!  I’ve been working diligently to migrate things over in the background so that the transition for you will be seamless.

There is one big item to note: Capsule is moving to an Open Auth process for access.  That’s a big enough deal that I’ll write a separate post on that.  For new users, that’s all you’ll ever see in the dashboard so no surprises for you.

For existing users, you’ll notice that your old credentials no longer appear.  They aren’t lost, they just aren’t being shown anymore.  I added a feature that would detect the credentials of existing users and use those to get updated Open Auth credentials so you won’t have any interruption in performance and it will be invisible to you.  That being said, it’s probably best that you at least familiarize yourselves with the new dashboard so that you aren’t surprised the next time you visit.

Another relatively minor change in how the API behaves is that Organisation names must now be unique.  In v1, each form submission that mapped to an Organisation would create a new Organisation, even if the name were identical to an existing one.  Now, in v2, that is no longer allowed.  If a site visitor types in the name of an existing Organisation, it won’t be created.  The Person and all other modules will work exactly as before.

I made a design decision to NOT connect the new Person to the existing Organisation because that would give any person with access to your form to add entries to your organisations that are unintended.  The default work flow will be that, if you truly did intend to link a new Person to an existing Organisation, you will do that from your Capsule dashboard.

As always, if you have any questions, feel free to contact me.