Skip to main content

Part 1–Create an Azure IoT Hub and Device

This is not AX but this was a nice experience. I worked through some labs to interact with Azure IoT Hub.

There is a lot of information out there on the web. So, I will focus on the the IoT Hub only here. On later dates, I may get into the other features of the IoT services in Azure.

Below are the steps to create a device in IoT Hub to get you started. After you have created your device, you can interact with the device in multiple ways.

Go to Azure and Create a new IoT Hub App.

2016-10-29_12-20-27

Enter the required information.

2016-10-29_12-21-50

Now you can Add Devices manually through the Azure Portal. Otherwise, you can use the SDK to add the device via code.

image

Now, I will show how to add the device via C#. Create a new Console project.

Add the reference via NuGet.

2016-10-29_12-27-16

Search for Microsoft.Azure.Devices and Install it.

2016-10-29_12-26-59

2016-10-29_12-27-41

Below is the code to copy and paste. Make sure to change the connection string to point it to your IoT Hub.

 using System;  
 using System.Collections.Generic;  
 using System.Linq;  
 using System.Text;  
 using System.Threading.Tasks;  
 using Microsoft.Azure.Devices;  
 using Microsoft.Azure.Devices.Common.Exceptions;  

 
 namespace CreateDeviceIdentity  
 {  
   class Program  
   {  
     static RegistryManager registryManager;  
     static string connectionString = "HostName=DAXIOTHUB.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=xxxxxxxx";  
     static void Main(string[] args)  
     {  
       registryManager = RegistryManager.CreateFromConnectionString(connectionString);  
       AddDeviceAsync().Wait();  
       Console.ReadLine();  
     }  
     private async static Task AddDeviceAsync()  
     {  
       string deviceId = "myFirstDevice";  
       Device device;  
       try  
       {  
         device = await registryManager.AddDeviceAsync(new Device(deviceId));  
       }  
       catch (DeviceAlreadyExistsException)  
       {  
         device = await registryManager.GetDeviceAsync(deviceId);  
       }  
       Console.WriteLine("Generated device key: {0}", device.Authentication.SymmetricKey.PrimaryKey);  
     }  
   }  
 }

Credit to Microsoft for the Labs. Lab doc I found was a little old but most of the steps worked.

Reference:

https://azure.microsoft.com/en-us/documentation/articles/iot-hub-csharp-csharp-getstarted/
Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more