@stevestevesteve are you saying you can’t see the files field that is associated with your Salesforce object? That is, it’s not available as something you can add to the fieldmap?
If so, one thing you might check is on the main settings tab for the plugin, there are checkboxes for whether to only use Salesforce objects that are updateable/triggerable (Salesforce’s words). You might try turning those off, if they are on, and see if that helps (clear the plugin cache first, if so).
If that does not help, it’s possible that you need to modify the permissions for the field in Salesforce. Salesforce is a complicated thing when it comes to permissions; I don’t know all the places where they can be modified. But if there’s a field that exists in Salesforce but you can’t see it in the dropdown, basically it boils down to:
1. It’s not triggerable/updateable but the plugin is set to ignore those
2. The permissions don’t allow it to be accessible via the API’s logged in user
3. It’s not available to the API at all
@jonathanstegall thanks for the quick reply.
Yes, that’s correct the files field that are associated with my object isn’t visible.
I didn’t think to check those fields, but i have just done so and neither of those options are checked so it can’t be that.
I will have a delve into the settings within Salesforce and hopefully there is something that can be done at that end to make the fields visible in WordPress.
If there is anything else i will re-post in this thread.
