Azure Functions allows you to write code that can be triggered by an event or timer. You don’t need a machine to run it on. All the computing runs on the Azure cloud ie sevrverless computing.
Below is a quick walk through. Keep in mind Microsoft has great documentation on their site. Just google it.
In this post I will put a simple walkthrough. Save you from the information overload.
Make sure you are using Visual Studio 2017.
Create a project of type “Azure Function”
Give it a minute to resolve the NuGet package. You will see a warning icon and watch it disappear by it self.
Once its done. Right click and Add item.
Select the type of function. The easiest to do is the Http trigger.
This will create a class with some sample code.
When you run it, it will run a local instance.
Navigate to the URL and watch it run.
There are many applications in the Dynamics space. Hopefully next time I can cover some Dynamics scenarios.
With the recent Platform update 10 they introduced server side coding and made some enhancements to the mobile platform. This brings a lot of flexibility and capabilities. Below I will focus on just the Expense Management Mobile workspace.
For one, the Mobile workspaces are now embedded in the AOT as a resource file. Notice how it says “In metadata”. This indicates that it has loaded from the AOT. I think this is a good move. Its all about ALM. This is also great to keep the server side and client side in sync.
The nice thing is that the Expense Mobile solution is in its own model. Makes it easy for us to track and learn from.
The main entry is the workspace resource file xml. Notice the guid, this is important for doing some server side coding.
Now lets take a look at the workspace class. You will notice the same guid is used for the class attribute.
in one of my prior posts, I mentioned that the currency field wasn’t being defaulted when entering a new expense. Now with server side coding you can achieve some of these things.
Below is a default config contract class. It is triggered from the above class. You can add as many contract classes as you like. See line 20 and 21 in the above screenshot.
If you look at the js file embedded in the workspace xml. You will notice that it loads the config contract onto the client side. Allowing it to work client side and not requiring a connection to the server.
The other things you will notice is that there are a number of forms created just for the mobile solution. Below are screenshots of the whole model. Its not that big but there has been substantial work done to get to this point.
Below are some screenshot for my own reference. I know I will refer to to it in the future.
Refer to Mobile Platform landing page for more information.
In this post I will describe how you can get the login dialog to pop up when you are developing a windows desktop application.
Below is an example of the dialog appearing.
Below is a sample code how to acquire the token.
string authorityUri = "https://login.windows.net/common/oauth2/authorize";Uri redirectURI = new Uri("https://login.live.com/oauth20_desktop.srf"); AuthenticationContext authenticationContext = new AuthenticationContext(authorityUri);AuthenticationResult authenticationResult = authenticationContext.AcquireTokenAsync( ClientConfig.Default.ActiveDirectoryResource, ClientConfig.Default.ActiveDirectoryClientAppId, redirectURI, new PlatformParameters(PromptBehavior.RefreshSession)).Result;
Add the redirect URI for https://login.live.com/oauth20_desktop.srf
D365O is a lot more sensitive about casting or should I say AX2012 was too relaxed about it. This post is to show a specific scenario that works differently in the new version of the product.
We had a bit of code that worked fine in AX2012 but stopped working in D365O. After debugging we found that when you cast a table it took the tableId of the cast.
Below is an example of AX2012 vs D365O:
I am very happy to say Daxeam Mobile is now available on Apple App store and Google Play Store. Daxeam Mobile fully working on both Dynamics 2012 and Dynamics 365 for Finance and Operations, Enterprise Edition.
Daxeam is an Enterprise Asset Management (EAM) solution available exclusively for Microsoft Dynamics AX 2012 and Dynamics 365 for Finance and Operations, Enterprise Edition. The Daxeam solution extends the functionality of AX, delivering integration to EAM across Projects, Inventory, Finance and Fixed Assets.
Some key items to note about the Mobile solution: