I try to keep focus on original content in this blog, but yesterday I read a post that was so interessting that I'd like to point it out.
The post is about the new possibilities you have for creating editor extensions to the X++ editor, as it is now hosted by Visual Studio.
Here's the link: http://dev.goshoom.net/en/2011/10/ax2012-editor-extensions/
A blog about any interesting "Microsoft Dynamics AX" and "Microsoft Dynamics 365 for Finance and Operations" stuff I come across.
Monday, October 24, 2011
Monday, October 10, 2011
Export and import labels for translation
If you develop solutions that need to be executed in several different languages you might need some external party to translate your label files, unless of course you are a linguistic genius.
I have written a small solution with a job that exports labels to a spreadsheet that you can send to an external party. When you get the spreadsheet back, you run a second job which based on the spreadsheet creates an XPO file. Now you can use the standard XPO import tool to analyze the changes and import the labels you want.
The jobs work on AX 2009. I have not tested them with other versions of AX.
You can find both jobs here:
I have written a small solution with a job that exports labels to a spreadsheet that you can send to an external party. When you get the spreadsheet back, you run a second job which based on the spreadsheet creates an XPO file. Now you can use the standard XPO import tool to analyze the changes and import the labels you want.
The jobs work on AX 2009. I have not tested them with other versions of AX.
You can find both jobs here:
Tuesday, October 4, 2011
Send invoices electronically
This is just a quick tip, as it seems to me that many are unaware of how easy it is to have Microsoft Dynamics AX 2009 and 2012 automatically send electronic customer invoices through AIF.
All you have to do is to setup AIF with a valid endpoint for the customer and the document. And you must select a print destination other than “Screen”. I’ll suggest you use “Print archive” as print destination if you don’t actually need the printed document. This will just add the documents to an internal queue that you delete later.
The \Classes\CustPrintOutInvoice\sendAsXML method will then take care of business, submitting the invoice to the AIF queue.
All you have to do is to setup AIF with a valid endpoint for the customer and the document. And you must select a print destination other than “Screen”. I’ll suggest you use “Print archive” as print destination if you don’t actually need the printed document. This will just add the documents to an internal queue that you delete later.
The \Classes\CustPrintOutInvoice\sendAsXML method will then take care of business, submitting the invoice to the AIF queue.
Subscribe to:
Posts (Atom)