Varun Arora - 2 years ago
Hi @Salesforce,Can you please release the same as this is affecting the Automation proess of Data Loading using CLI.
If anybody wants to automate the processs of uploading the Accounts, then Opportunities and then Past Activities from the legacy System, then it is becoming a serious problem when the turn comes of Task or Events as we can't associate the Task to Opportunity or Account due to Polymorphic field.This is forcing us to shift to Apex trigger on the Task/Event object to have that linkage..
Jeff Helm - 2 years ago
Because I have about 100 users of my system all over my state. Some users will have interactions with members (Accounts) outside of our Salesforce system and will send me this data that doesn't contain an internal ID because they consider the External ID we use (which is what the member (Account) knows) and I have to first match up the data to the internal ID before I can import it. It is a step that I would really like to avoid as it takes as long or longer than to upload the data.
This would be a huge help.
Thanks for your consideration.
Jake Hebert - 4 years ago
Just ran into a use case where I'm trying to switch an attachment from one object to another in the trigger. (Which is actually a workaround for the Salesforce limitation of not supporting EmailMessages in platform encryption, but that's a whole different thing).
Now I have to do another query and build a map for something that already has an external ID which, if this existed, I could just directly reference. Just reinforcing my opinion that polymorphic lookups are the worst thing salesforce has ever come up with and responsible for most of my Apex stress nightmares...