Closed (won't fix)
Project:
Salesforce Suite
Version:
7.x-3.x-dev
Component:
salesforce_push.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Nov 2013 at 18:29 UTC
Updated:
21 Feb 2026 at 19:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
aaronbaumanHere's a basic change.
It's not practical to remove this property entirely, because we don't have reliable identifying information for entity create operations.
So, salesforce_pull still uses the property internally, but salesforce_push doesn't have to bother with it.
Not as big a change I was expecting.
I'll leave this open for a couple days for comments, then commit it.
Comment #2
tauno commentedLooks like just a different way of doing the same thing. Not sure there's value in implementing our own hook rather than just doing the check in the appropriate place. Is there another reason to make this change?
Comment #3
aaronbaumanI guess the only reason is to better encapsulate SF Pull's behavior.
Yes, it's another way to do the same thing, but it makes salesforce_push_entity_crud() a bit cleaner.
Comment #4
aaronbauman7.x is no longer supported