Hi ​@Skama Thanks for stopping by the community! I asked our tech team about this, and they sent me the following instructions for you to try. You can also find them here!

• Log in to your SF account as the admin of your Salesforce organization
• Once logged in, you can add the following to the URL, /packaging/installPackage.apexp?p0=04t5a000001HyqnAAC, after your SF subdomain.
• E.g. on my test account, the URL is https://typeform-dev.lightning.force.com, and to run the new package it has to look like: https://typeform-dev.lightning.force.com/packaging/installPackage.apexp?p0=04t5a000001HyqnAAC

Hopefully this helps, but let me know if this doesn’t work!

Hi ​@Liz ,
Thanks for your reply. I was able to install in sandbox and verify forms and mappings looked ok after the upgrade to 1.25.

However after I put it in production today we get an error for every lead inserted : “Attempt to de-reference a null object”.

What would be the cause of these errors in the new version of Typeform connector?

Thanks

Hi ​@Skama Ah glad to hear it’s working for you! As for the error, this error is triggered when a required field in Salesforce receives a null value in Typeform (empty URL parameters are also treated as null values).

To work around this issue, create a manual record in Salesforce for the response with null values. Delete the corresponding response from the Responses panel in Typeform. Then, run the Retrieve Responses job in Salesforce again.

Let me know if that doesn’t fix it (if you haven’t fixed it already)!

Hi, 

In fact the error was due to the new version and the work around advised by support is to delete and redo the mappings (exactly as before). It worked fine for us but it takes time to redo all mappings after an update of the package.

 

Yeah, I definitely get that frustration, ​@Skama . I’ll share that feedback with our integrations team.