New Wordpress object is not pushed to Salesforce if Salesforce user can create but can't edit records

[jose-dvm]

Describe the bug

Hi, I was trying to setup a Leads push and I noticed that when using a Salesforce user who can create Leads but cannot edit them, the plugin doesn't push the new Wordpress record to Salesforce. Adding Edit permission to the user solves this, but it prevents to use a least privileges possible policy and results in a confusing UX.

To Reproduce
Steps to reproduce the behavior:

1. Create a Fieldmap to push some Wordpress object as Salesforce Leads using a Salesforce user who can create but not edit Leads. Probably Salesforce fields will be displayed as Locked.
2. Create the Wordpress record
3. Push won't be performed and a debug log will be created if this is setup

Expected behavior
If the Salesforce user can create records, new Wordpress records should be pushed to Salesforce.

Screenshots

Screenshot of ignored push log:

Environment (please complete the following information):

• WordPress Version: 6.4.5
• PHP Version 7.4.33

Additional context

I think this is due to considering as locked / read-only fields those who are not updateable, even when they are createable.
See this in Fiedmap page and the next one used in push class:

object-sync-for-salesforce/templates/admin/fieldmaps-add-edit-clone.php

Line 310 in 9e4535e

if ( false === $salesforce_field['updateable'] ) {

object-sync-for-salesforce/classes/class-object-sync-sf-mapping.php

Line 1096 in 9e4535e

if ( 1 !== (int) $fieldmap['salesforce_field']['updateable'] ) {

[jonathanstegall]

That is interesting. I'm not sure if that is the reason, but it's possible. No one is currently working on this plugin, but if there is a fix, it could be possible to implement. Do you have a sense of whether the Salesforce API has a method for detecting whether a field is createable?