Service Azure qui automatise l’accès et l’utilisation des données dans les clouds sans écrire de code.
Hello M.Altaf,
Thank you for your welcoming.
We have already evaluated the use of the generic HTTPS action from Logic Apps and we are indeed using this approach in several workflows.
However, one of the advantages of the official Salesforce connector is its ability to automatically expose Salesforce objects and operations, making development much easier. This is why our developers are more comfortable using the official connector rather than building and maintaining custom REST calls.
When using the HTTP approach, we lose this object discovery experience and need to manually manage Salesforce APIs, endpoints, payloads, metadata and authentication.
Do you have any recommendations or best practices to achieve a similar developer experience while avoiding the official connector ?
Our goal is to adopt a secure OAuth application authentication model without losing the productivity benefits that the official Salesforce connector currently provides.
Moreover, as this capability was not mentioned in your response, may we assume that there is currently no publicly announced roadmap item for supporting OAuth application authentication (e.g. Connected App / Client Credentials) in the official Salesforce connector?
Thank you for your guidance and your quick response.
Have a good day !