The composite tree resource always creates new records, which is why it gives you that behavior. Instead, you'd use a composite request. This example gives you the closest behavior you have available. You'd start by using a GET /services/data/v48.0/sobjects/Account/External_Id__c/x165, which returns the account, then use that reference in further updates.
You can add expression as external Id field in Informatica field mapping like this:
In Salesforce, Create a text field of unique, external Id type.
In Informatica, Choose operation type as: Upsert (Update or Insert)
In Informatica, field Mapping map the external Id field to this expression Firstname||'_'||Lastname||'_'||Email
Now Informatica will ...
It depends on what you're trying to accomplish.
If your goal is to have users sign in to SF with their AD credentials, you can implement single sign-on (SSO) via SAML or OpenID Connect using your favorite commercial or open source product. Commercial product - license is going to be more expensive vs Identity Connect. Open Source - if you can handle it, ...
You don’t need multi org for this. What you need to be aware of is:
Integration user in SFMC needs to have access to all the relevant BUs (this is far the most common cause of the issue you are facing). You do this by looking up the user in Setup > Users > Users:
Check the box next to the user and click on Manage Business Units. You get to this page, where ...
Here is the configuration I have to have Salesforce 2 calling Salesforce 1 API:
In Salesforce 2: Named Credentials
Certificate: using one created from Salesforce 2 (Certificates and Key Management)
Identity Type: Per User
Authentication Protocol: JWT Token Exchange
Token Endpoint URL: https://login.salesforce.com/services/oauth2/token
Scope: api web ...
Your question is very broad and lacks specifics. Because we do not have information about the setup but here are a couple of things I can recommend apart from writing your own code.
Using ODATA - You can download the Microsoft OData Source and use the your DB as an external object. No need for any connectors or other tools. You data will be available in ...
Auto number is an auto-calculated read-only field and although you can set it as External Id, it cannot be used for upserting record.
Refer to extracts below from this Salesforce article which describes the behavior for Data loader upsert and this also applies for Mulesoft integration.
As a workaround, consider having an editable field instead as External ...