Skip to main content

My first Dynamics AX 2012 Windows 8 App

I have recently created my first Windows 8 App and I thought I would write about my experience.

My first starting point is to download this Starter Kit.

Dynamics AX 2012 Windows 8 App Developer Starter Kit

http://startwindaxapp.codeplex.com/

Then before you do this I would suggested you have a look at Martin’s blog. He has made some fixes.

http://dev.goshoom.net/en/2013/03/ax2012-win-8-starter-kit/

Create a custom web service

First task was to create a web service. I didn’t want to use a Document service. So, I created a custom service.

I wont go through the details of creating a contract or anything but I will show what the method I need is.

2013-11-07_1441

Create a windows 8 app

With visual studio 2012 (latest update 3 installed) I created a new project of type Windows Store.

This Grid view will create 3 *.xmal pages. See the screenshot below there is a preview on the right hand side. It shows a Grid view, a Group view, and a Item detailed view.

2013-11-07_1445

This is where we call the web service to retrieve the list. In my code I have not gotten into the detail but that is already in the sample. The sample uses a document service but I wanted some thing a bit more tightly coupled (custom web service).

2013-11-07_1450

Now when you run it it will look like this below. The 3 *.xmal pages will work with the default code provided.

2013-11-07_1453

2013-11-07_1454

2013-11-07_1454_001

The ease of creating the web service and external applications is leaps and bounds better than before. If you have people that are very capable with Win8 apps / mobile etc. Then they would love what there is to offer.

The other thing you have to realise also is – windows 8 is a lot more stronger with design aspect. They have rules and quality bars that you have to meet to release into the app store. I think this is a good step.

References:

Detail on creating a custom web service in AX.

http://tech.alirazazaidi.com/exploring-the-little-complex-custom-service-in-dynamics-ax-2012/

Dynamics AX 2012 Windows 8 App Developer Starter Kit

http://startwindaxapp.codeplex.com/

Then before you do this I would suggested you have a look at Martin’s blog. He has made some fixes.

http://dev.goshoom.net/en/2013/03/ax2012-win-8-starter-kit/

For secure web service via Azure follow these articles.
Developing Secure Mobile Apps for Dynamics AX 2012 - Connector
http://code.msdn.microsoft.com/Developing-Secure-Mobile-b6ba16a2
Developing Secure Mobile Apps for Dynamics AX 2012
http://code.msdn.microsoft.com/Developing-Secure-Mobile-02105158

Demo video with technical aspects – Interesting because they talk about the standard solution and what they did.

They used HTML file to make it flexible cross platform using their own libraries. Wish they released these libraries and projects the same way AX is open.
http://channel9.msdn.com/Events/Build/2013/2-9193

Sample App with Code
http://code.msdn.microsoft.com/Developing-Secure-Mobile-02105158

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.

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: ...

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...