Timeline for Different user IDs across production and sandboxes - how to make them the same for every user?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2013 at 14:29 | answer | added | Matthew Lamb | timeline score: 5 | |
| Jun 7, 2013 at 14:04 | history | tweeted | twitter.com/#!/StackSalesforce/status/343005446954704897 | ||
| Jun 6, 2013 at 13:21 | comment | added | Steven Herod | Some of these comments could/should be answers :) | |
| Jun 6, 2013 at 12:26 | comment | added | techtrekker | You can create a new External Id field on User, and stamp that with the Id from Production. You can then use this External Id field for any mapping with your tool. | |
| Jun 6, 2013 at 10:11 | comment | added | drakored | If you use SAML for single sign on the FederatedIdentifier field would work wonders for this purpose. | |
| Jun 6, 2013 at 10:04 | comment | added | nisseknudsen | Thanks, I expected that answer... :( I am not hardcoding the ID, it is for an external support tool, where we connect customer users to our CRM contacts. The ideal case is to have (independent of any org derivate (e.g., production, sandbox)) for each user one contact and one portal user. | |
| Jun 6, 2013 at 10:02 | comment | added | drakored | No, the only way is by refreshing. What are you doing that requires the Id to be the same? Best practices are to not tie anything to a hard coded Id. | |
| Jun 6, 2013 at 9:49 | history | asked | nisseknudsen | CC BY-SA 3.0 |