Multiple Reocords - Create
Create multiple, unrelated Salesforce records of the same type using SQL Server
- See SQLHTTP easy setup for Salesforce
- See API Call documentation for parameter values and other information
- Create the stored procedure documented below
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
CREATE PROCEDURE usp_SalesForce_Multiple_Records_Create( @Profile nvarchar(100), @APIVersion varchar(6), @Record varchar(20), @Body varchar(MAX), @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS IF @APIVersion NOT LIKE 'v[0-9]%' BEGIN RAISERROR('Invalid API Version. Example: v20.0', 16, 1) RETURN END IF ISNUMERIC(SUBSTRING(@APIVersion, 2, LEN(@APIVersion))) = 0 BEGIN RAISERROR('Invalid API Version. Example: v20.0', 16, 1) RETURN END DECLARE @URL nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = SQLHTTP.net.AuthParam(@Profile, 'InstanceURL') EXEC SQLHTTP.net.UrlBuilder @URL OUTPUT, @Profile, 'services', 'data', @APIVersion, 'composite', 'tree', @Record EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC usp_Salesforce_Auth_Header @Profile, @HTTPSessionID EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'POST', @Body = @Body, @ContentType = 'application/json', @Accept = 'application/json', @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT, @Response = @Response OUTPUT GO |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 |
DECLARE @Response nvarchar(MAX) DECLARE @StatusCode int DECLARE @StatusDescription nvarchar(MAX) DECLARE @Body varchar(MAX) DECLARE @Profile nvarchar(100) SET @Profile = 'My Salesforce' SET @Body = '{ "records" :[{ "attributes" : {"type" : "Account", "referenceId" : "ref1"}, "name" : "SampleAccount1", "phone" : "1111111111", "website" : "www.salesforce1.com", "numberOfEmployees" : "100", "industry" : "Banking" },{ "attributes" : {"type" : "Account", "referenceId" : "ref2"}, "name" : "SampleAccount2", "phone" : "2222222222", "website" : "www.salesforce2.com", "numberOfEmployees" : "250", "industry" : "Banking" },{ "attributes" : {"type" : "Account", "referenceId" : "ref3"}, "name" : "SampleAccount3", "phone" : "3333333333", "website" : "www.salesforce3.com", "numberOfEmployees" : "52000", "industry" : "Banking" },{ "attributes" : {"type" : "Account", "referenceId" : "ref4"}, "name" : "SampleAccount4", "phone" : "4444444444", "website" : "www.salesforce4.com", "numberOfEmployees" : "2500", "industry" : "Banking" }] }' --Salesforce Bearer Token is valid for only a few hours EXEC usp_Salesforce_Auth_Refresh @Profile EXEC usp_SalesForce_Multiple_Records_Create @Profile = @Profile, @APIVersion = 'v40.0', @Record = 'Account', @Body = @Body, @Response = @Response OUTPUT, @StatusCode = @StatusCode OUTPUT, @StatusDescription = @StatusDescription OUTPUT IF @StatusCode >= 400 EXEC SQLHTTP.net.RaiseHttpError @StatusCode, @StatusDescription, @Response ELSE BEGIN DECLARE @X xml SET @X = SQLHTTP.net.Json_To_Xml(@Response, '0') --The XPath syntax below was easily generated by executing the following commands: --EXEC SQLHTTP.net.XQueryHelper @X --and then executing: --EXEC SQLHTTP.net.XQueryHelper @X, 'JsonObject/results/JsonObject' SELECT T.C.value(N'@id', N'nvarchar(MAX)') AS [id] ,T.C.value(N'@referenceId', N'nvarchar(MAX)') AS [referenceId] FROM @X.nodes(N'/JsonObject/results/JsonObject') T(C) END |
1 2 3 4 5 6 7 8 |
id referenceId -------------------- ---------------- 0010Y00000ZLWFXQA5 ref1 0010Y00000ZLWFYQA5 ref2 0010Y00000ZLWFZQA5 ref3 0010Y00000ZLWFaQAP ref4 |
- Account Information – Fetch
- Deleted Records – Fetch
- Domain – Search
- Email – Fetch
- Email Count – Fetch
- Email Verification – Fetch
- Lead – Create
- Lead – Delete
- Lead – Update
- Leads – Fetch
- Leads List – Create
- Leads List – Delete
- Leads List – Fetch
- Leads List – Update
- Leads Lists – Fetch
- Multiple Reocords – Create
- Multiple Requests – Create
- Nested Records – Create
- Recently Viewed Records – Fetch
- Records as Recently Viewed – Query
- Relevant Items – Fetch
- Search Scope and Order – Fetch
- String – SOSL Search
- Updated Records – Fetch
IMPORTANT DISCLAIMER
CODE/SQL ON THESE PAGES ARE PROVIDED AS-IS AND ARE AVAILABLE FOR ILLUSTRATIVE PURPOSES ONLY.
USERS ARE REQUIRED TO ABIDE BY THE TERMS AND CONDITIONS FOR USING REFERENCED THIRD PARTY WEBSITES AND/OR APIs FROM THEIR RESPECTIVE WEBSITES. WE DO NOT CONDONE ANY VIOLATION OF THIRD PARTY WEBSITES AND/OR APIs TERMS AND CONDITIONS USING OUR SOFTWARE.
USERS SHALL BE SOLELY RESPONSIBLE AND BE SOLELY LIABLE FOR VIOLATION OF ANY RULES SPECIFIED BY THIRD PARTIES FOR USING THEIR WEBSITES AND/OR APIs, OR INFRINGEMENT OF RIGHTS OF SUCH THIRD PARTIES.