Override - Create
Create a Sender Override in Microsoft Outlook using SQL Server
- See SQLHTTP easy setup for Microsoft Graph
- 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 |
CREATE PROCEDURE usp_MicrosoftGraph_Override_Create( @Profile varchar(100), @Body varchar(MAX), @Response nvarchar(MAX) OUTPUT, @StatusCode int OUTPUT, @StatusDescription nvarchar(MAX) OUTPUT) AS DECLARE @URL nvarchar(MAX) DECLARE @HTTPSessionID uniqueidentifier SET @URL = 'https://graph.microsoft.com/v1.0/me/inferenceClassification/overrides' EXEC SQLHTTP.net.HTTPSession @HTTPSessionID OUTPUT EXEC usp_MicrosoftGraph_Auth_Header @Profile, @HTTPSessionID EXEC SQLHTTP.net.HTTPRequest @HttpSessionID, @URL = @URL, @Method = 'POST', @Body = @Body, @ContentType = '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 |
DECLARE @Response nvarchar(MAX) DECLARE @StatusCode int DECLARE @StatusDescription nvarchar(MAX) DECLARE @Profile varchar(100) = 'My Microsoft Graph' DECLARE @Body varchar(MAX) SET @Body = '{ "classifyAs": "focused", "senderEmailAddress": { "name": "Samantha Booth", "address": "samanthab@adatum.onmicrosoft.com" } }' --Microsoft Graph API Bearer Token expires after an hour EXEC usp_MicrosoftGraph_Auth_Refresh @Profile EXEC usp_MicrosoftGraph_Override_Create @Profile = @Profile, @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' SELECT T.C.value(N'@id', N'nvarchar(MAX)') AS [id] ,T.C.value(N'@classifyAs', N'nvarchar(MAX)') AS [classifyAs] ,T.C.value(N'senderEmailAddress[1]/@address', N'nvarchar(MAX)') AS [sender_address] ,T.C.value(N'senderEmailAddress[1]/@name', N'nvarchar(MAX)') AS [sender_name] FROM @X.nodes(N'/JsonObject') T(C) END |
|
1 2 3 4 5 |
id classifyAs senderEmailAddress_name senderEmailAddress_address ------------------- ------------ ------------------------- --------------------------------- 54fc9f96-a74d-... focused Samantha Booth samanthab@adatum.onmicrosoft.com |
- Calendar – Create
- Calendar Group – Create
- Calendar Groups – Fetch
- Calendar Open Extension – Create
- Calendar View – Fetch
- Calendars – Fetch
- Contact – Create
- Contact – Fetch
- Contact – Update
- Contact Child Folder – Create
- Contact Child Folders – Fetch
- Contact Folder – Create
- Contact Folder – Fetch
- Contact Folder – Update
- Contact Folders – Fetch
- Contacts – Fetch
- Drive – Fetch
- DriveItems – Fetch
- Event – Create
- Event – Fetch
- Event – Update
- Events – Fetch
- Mail – Send
- Mail Child Folder – Create
- Mail Child Folders – Fetch
- Mail Folder – Copy
- Mail Folder – Create
- Mail Folder – Delete
- Mail Folder – Move
- Mail Folder – Update
- Mail Folders – Fetch
- Message – Copy
- Message – Create
- Message – Create Draft
- Message – Create Forward
- Message – Create Reply
- Message – Create ReplyAll
- Message – Delete
- Message – Fetch
- Message – Forward
- Message – Move
- Message – Reply
- Message – ReplyAll
- Message – Send
- Message – Update
- Message File Attachment – Add
- Message File Attachment – Fetch
- Message Item Attachment – Add
- Message Item Attachment – Fetch
- Messages – Fetch
- Notebook – Create
- Override – Create
- Override – Delete
- Override – Update
- Overrides – Fetch
- People – Fetch
- Person – Fetch
- Reminder View – Fetch
- User – Fetch
- Users – 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.