Work with SalesForce APIs via the Eloquent Model.
Install via composer
composer require rob-lester-jr04/eloquent-sales-force
Note! This and next step are optional if you use laravel>=5.5 with package auto discovery feature.
Add service provider to config/app.php
in providers
section
Lester\EloquentSalesForce\ServiceProvider::class,
**Note that this is optional and in most cases, the configuration here is not needed.
php artisan vendor:publish --provider="Lester\EloquentSalesForce\ServiceProvider" --tag="config"
- Log into to your Salesforce org
- Click on Setup in the upper right-hand menu
- Under Build click
Create > Apps
- Scroll to the bottom and click
New
under Connected Apps. - Enter the following details for the remote application:
- Connected App Name
- API Name
- Contact Email
- Enable OAuth Settings under the API dropdown
- Callback URL
- Select access scope (If you need a refresh token, specify it here)
- Click
Save
After saving, you will now be given a Consumer Key and Consumer Secret. Update your config file with values for consumerKey
, consumerSecret
, and loginURL
.
In your config/database.php
file, add the following driver to the connections array
'soql' => [
'driver' => 'soql',
'database' => null,
'consumerKey' => env('CONSUMER_KEY'),
'consumerSecret' => env('CONSUMER_SECRET'),
'loginURL' => env('LOGIN_URL'),
// Only required for UserPassword authentication:
'username' => env('USERNAME'),
// Security token might need to be ammended to password unless IP Address is whitelisted
'password' => env('PASSWORD')
],
If you need to modify any more settings for Forrest, publish the config file using the artisan
command:
php artisan vendor:publish
You can find the config file in: config/eloquent_sf.php
. Any of the same settings that Forrest recognizes will be available to set here.
Create a model for the object you want to use, example: artisan make:model Lead
Open the model file, it will look like this:
<?php
namespace App;
use Illuminate\Database\Eloquent\Model;
class Lead extends Model
{
//
}
Replace the use
statement so your model looks like:
<?php
namespace App;
use Lester\EloquentSalesForce\Model;
class Lead extends Model
{
//
}
Now use it like you normally would!
$leads = Lead::where('email', '[email protected]')->get();
$lead = Lead::find('00Q1J00000cQ08eUAC');
Update properties like you normally would...
$lead->FirstName = 'Robert';
$lead->save();
$lead = new Lead();
$lead->FirstName = 'Foo';
$lead->LastName = 'Bar';
$lead->Company = 'Test';
$lead->save();
OR:
$lead = Lead::create(['FirstName' => 'Foo', 'LastName' => 'Bar', 'Company' => 'Test Company']);
$leads = collect([
new Lead(['Email' => '[email protected]']),
new Lead(['Email' => '[email protected]'])
]);
Lead::insert($leads);
$lead = Lead::first();
$lead->LastName = 'Lester';
$lead->save();
OR:
$lead->update(['LastName' => 'Lester']);
The bulk update method is model agnostic - meaning that this capability, within salesforce, accepts a mix of object types in the collection that gets sent. So this method therefore exists in the new SObjects facade.
$accounts = Account::where('Company', 'Test Company')->get(); // collection of accounts.
$accounts = $accounts->map(function($account) {
$account->Company = 'New Company Name';
return $account;
});
SObjects::update($accounts); // Sends all these objects to SF with updates.
SalesForce will execute each update individually and will not fail the batch if any individual update fails. If you want success to be dependent on all updates succeeding (all or nothing), then you can pass true
as the second parameter. If this is set, the batch of updates must all succeed, or none will.
SObjects::update($accounts, true); // All or none.
By default, the object is loaded with the columns found in the primary compactLayout. If you'd like additional columns, you would use the select
method on the model. For example:
$leads = Lead::select('Id', 'Name', 'Email', 'Custom_Field__c')->limit(10)->get();
The where
and orderBy
methods work as usual as well.
$contacts = Contact::where('Email', '[email protected]')->first();
$contacts = Contact::where('Name', 'like', 'Donuts%')->get();
$contacts = Contact::limit(20)->orderBy('Name')->get();
Exactly as you'd expect.
$lead = Lead::first();
$lead->delete();
Relationships work the same way.
Create a model like above for Account
and Contact
In the Contact
model, add a method for a relationship like you normally would
## Contact.php
public function account()
{
return $this->belongsTo(Account::class);
}
So you can call now:
$contact = Contact::where('email', '[email protected]')->first();
$account = $contact->account;
And the reverse is true
## Account.php
public function contacts()
{
return $this->hasMany(Contact::class);
}
$contacts = $account->contacts;
You are also able to use manual joins
$account = Account::join('Contact', 'AccountId')->first();
These aren't as easy to work with as Relationships because the SalesForce API still returns the array nested in the records
property.
To use custom objects (or an object with a special object name, different from the model), set the protected $table
property in the model.
<?php
namespace App;
use Lester\EloquentSalesForce\Model;
class TouchPoint extends Model
{
protected $table = 'TouchPoint__c';
/** Any other overrides **/
}
This is a new feature to the package. The SObjects facade serves the purpose of exposing any global features not model specific, such as authentication and mass updates, but also it is a pass-thru mechanism for the Forrest facade.
Any methods such as get, post, patch, resources, etc will pass through to the Forrest facade and accept parameters respectively.
The authenticate()
method in the facade will return the token information that has been stored in cache/session.
If you discover any security related issues, please email instead of using the issue tracker.
This package is bootstrapped with the help of melihovv/laravel-package-generator.