AutoIt
AutoIt
Azure Table Insert Entity
See more Azure Table Service Examples
Insert an entity into an Azure table.Chilkat AutoIt Downloads
Local $bSuccess = False
; This example requires the Chilkat API to have been previously unlocked.
; See Global Unlock Sample for sample code.
$oRest = ObjCreate("Chilkat.Rest")
; IMPORTANT: Make sure to change "myaccount" to your actual Azure Storage Account name.
; IMPORTANT: Also change "mytable" to the name of your Azure table.
; We're going to POST to this URL: https://myaccount.table.core.windows.net/mytable
Local $bTls = True
Local $iPort = 443
Local $bAutoReconnect = True
$bSuccess = $oRest.Connect("myaccount.table.core.windows.net",$iPort,$bTls,$bAutoReconnect)
If ($bSuccess <> True) Then
ConsoleWrite("ConnectFailReason: " & $oRest.ConnectFailReason & @CRLF)
ConsoleWrite($oRest.LastErrorText & @CRLF)
Exit
EndIf
; Provide Azure Cloud credentials for the REST call.
$oAzAuth = ObjCreate("Chilkat.AuthAzureStorage")
$oAzAuth.AccessKey = "AZURE_ACCESS_KEY"
; The account name used here should match the 1st part of the domain passed in the call to Connect (above).
$oAzAuth.Account = "myaccount"
$oAzAuth.Scheme = "SharedKey"
$oAzAuth.Service = "Table"
; This causes the "x-ms-version: 2019-07-07" header to be automatically added.
$oAzAuth.XMsVersion = "2019-07-07"
$bSuccess = $oRest.SetAuthAzureStorage($oAzAuth)
; Note: The application does not need to explicitly set the following
; headers: Content-Length, x-ms-date, Authorization. These headers
; are automatically set by Chilkat.
; Note: The above code does not need to be repeatedly called for each REST request.
; The rest object can be setup once, and then many requests can be sent. Chilkat will automatically
; reconnect within a FullRequest* method as needed. It is only the very first connection that is explicitly
; made via the Connect method.
; Use this online tool to generate code from sample JSON:
; Generate Code to Create JSON
; The following JSON is sent in the request body.
; {
; "PartitionKey":"mypartitionkey",
; "RowKey":"myrowkey",
; "Timestamp":"2013-08-22T01:12:06.2608595Z",
; "Address":"Mountain View",
; "Age":23,
; "AmountDue":200.23,
; "CustomerCode":"c9da6455-213d-42c9-9a79-3e9149a57833",
; "CustomerSince":"2008-07-10T00:00:00",
; "IsActive":true,
; "NumberOfOrders":"255"
; }
$oJson = ObjCreate("Chilkat.JsonObject")
$oJson.UpdateString("PartitionKey","mypartitionkey")
$oJson.UpdateString("RowKey","myrowkey")
$oJson.UpdateString("Timestamp","2013-08-22T01:12:06.2608595Z")
$oJson.UpdateString("Address","Mountain View")
$oJson.UpdateInt("Age",23)
$oJson.UpdateNumber("AmountDue","200.23")
$oJson.UpdateString("CustomerCode","c9da6455-213d-42c9-9a79-3e9149a57833")
$oJson.UpdateString("CustomerSince","2008-07-10T00:00:00")
$oJson.UpdateBool("IsActive",True)
$oJson.UpdateString("NumberOfOrders","255")
; IMPORTANT: Pay attention to the options for nometadata, minimalmetadata, or fullmetadata.
; See the Azure table service API documentation at https://docs.microsoft.com/en-us/rest/api/storageservices/insert-entity
$oRest.AddHeader("Accept","application/json;odata=nometadata")
$oRest.AddHeader("Prefer","return-no-content")
$oRest.AddHeader("Content-Type","application/json")
$oSbRequestBody = ObjCreate("Chilkat.StringBuilder")
$oJson.EmitSb($oSbRequestBody)
$oSbResponseBody = ObjCreate("Chilkat.StringBuilder")
; IMPORTANT: Change "mytable" to the name of your actual table.
$bSuccess = $oRest.FullRequestSb("POST","/mytable",$oSbRequestBody,$oSbResponseBody)
If ($bSuccess <> True) Then
ConsoleWrite($oRest.LastErrorText & @CRLF)
Exit
EndIf
; A status code of 204 is a success response for the case where Prefer=return-no-content.
Local $iRespStatusCode = $oRest.ResponseStatusCode
ConsoleWrite("Response Status Code = " & $iRespStatusCode & @CRLF)
If ($iRespStatusCode >= 400) Then
ConsoleWrite("Response Header:" & @CRLF)
ConsoleWrite($oRest.ResponseHeader & @CRLF)
ConsoleWrite("Response Body:" & @CRLF)
ConsoleWrite($oSbResponseBody.GetAsString() & @CRLF)
Exit
EndIf
ConsoleWrite("Success." & @CRLF)