Salesforce API: Cannot map to 'Website' field at Salesforce Leads about forms-3rdparty-integration HOT 6 CLOSED

Sorry, I don't have a Salesforce account to test this against. As long as SF exposes a website field, it should post. You'd have to take it further with Salesforce themselves.

Also, I would expect sending XML to a JSON endpoint not to work...

from forms-3rdparty-integration.

Hey Zaus,
As far as not having a SF account, no worries.

However the second issue isn't about sending XML to JSON. It's when I install the XML plugin and don't configure it for anything, it breaks my JSON connection I previously setup to SF. So once the XML plugin is installed then JSON connections no longer work even if they were previously working.

This is a pretty big bug as my interpretation of the XML plugin is that it simply allows you to create XML API connections, but should not break any previously setup JSON connections. Unless the XML plugin is designed to take over the entire original plugin and make it XML only then this is a problem.

from forms-3rdparty-integration.

Ah...I see. Yes, you're right -- the XML post plugin does take over for all submissions. Can you file a bug/feature request on that github repo and reference this ticket? The problem likes with the fact that you can uncheck "as xml", but it's still nesting the request body -- https://github.com/zaus/forms-3rdparty-xpost/blob/master/forms-3rdparty-xpost.php#L58 -- and only later checks the setting at https://github.com/zaus/forms-3rdparty-xpost/blob/master/forms-3rdparty-xpost.php#L77.

For now, you can modify the plugin file to fix this, something like adding around line 44 (at the beginning of the method):

if( ! isset($service[self::PARAM_ASXML]) ||  'true' != $service[self::PARAM_ASXML]) return $args;

which should let you conditionally use the extension per service properly.

from forms-3rdparty-integration.

As you can see, I just made the issue request on the other plugin.

from forms-3rdparty-integration.

Thanks zaus!

from forms-3rdparty-integration.

hey @Computergiant -- can you try out v0.4 of xpost and let me know if that fixes your problem? If so please close the issue over there...

from forms-3rdparty-integration.