Added ability to override the service end point for allowing the use of ...

[RokitSalad]

...custom rest services for specific entities. The one gocha is that any errors returned from the custom service must be formatted in a similar fashion as the standard rest end points.

[giacomelli]

Can you provide me a sample using an alternative url? I would like to improve the documentation with this sample.

Thanks!

[RokitSalad]

Sure.

For example, when creating a new user, your SalesforceClient.Create method would be called as:

    _client.Create("CW_User", new { Username = username, ContactId = _contactId, Email = "a@a.com", FederationId = Guid.NewGuid() }, "services/apexrest");

where CW_User is a custom entity exposed at a restful endpoint of /services/apexrest/CW_User

With the change I made, any of the Create, Update, Query or FindById methods will accept an alternative url as an optional final parameter. SalesForce allows custom REST services to be exposed so further business logic can be abstracted away. The change allows the normal end point to be used when an alternative url isn't specified but be overridden when a custom end point is needed.

    private SalesforceClient _client;
    public void CreateContactWithCustomUser(string firstName, string lastName)
    {
        string contactId = _client.Create("Contact", new { FirstName = firstName, LastName = lastName });
        _client.Create("CW_User", new { Username = username, ContactId = contactId, Email = "a@a.com", FederationId = Guid.NewGuid() }, "services/apexrest");
    }

In this example, a contact is created as normal but the user is created at the end point services/apexrest/CW_User. The service exposed at this point has been written to implement some custom logic that isn't provided by the standard /User REST service.

Hope that helps :)

[giacomelli]

Ok, great new feature.
Tks!

[giacomelli]

Added a FAQ question linking for your explanation: https://github.com/giacomelli/SalesforceSharp/wiki/FAQ
;)

[RokitSalad]

Cheers :)