There is the commande for installing the PowerShell module on your computer:
# EXECUTE THIS IN POWERSHELL WITH "RUN AS ADMINISTRATOR" OPTION
# AUTHORIZE REMOTE SIGNED COMMAND
# IMPORT THE POWERSHELLGET MODULE
# INSTALL THE AZURE MODULE
Install-Module Azure -Force -AllowClobber
Install-Module AzureRM -Force -AllowClobber
# UPDATE THE POWER SHELL HELP
From PurchLine or SalesLine for example:
Using the option #localmacro can reduce the size and also the visibility of your code.
For example, you create a while select statement and you have to control date range when some value are enable (so not all the time)
You can write this kind of code :
protected void doProcess()
(salesTable.DeliveryDate >= fromDate && salesTable.DeliveryDate <= toDate)
(custPackingSlipJour.DeliveryDate >= fromDate && custPackingSlipJour.DeliveryDate <= toDate)
while select salesTable
where (!validatedOrTransmited || ((salesTable.MySalesStatus == MyStatus::Transmission
|| salesTable.MySalesStatus == MyStatus::Validation))
&& (!prepared || (salesTable.MySalesStatus == MyStatus::Prepare
&& (!delivered || (salesTable.MySalesStatus == MyStatus::Delivery))
exists join firstOnly custPackingSlipJour
where custPackingSlipJour.SalesId == salesTable.SalesId
&& (!delivered || #CheckDateDocument)
// code here.
Description of the article :
Three years ago, the Premier Field Engineer team started the delivery of the Dynamics AX Code Review for Premier customers. It has been quite an interesting journey seeing many customization from different instances. Today I would like to step back and reflect on some of the most common issues.
If you are a senior developer on Dynamics AX, you may wonder how come these issues still exist. This is the reason why I decided to write this article. Developments are now shared among diverse team, sometimes across multiple partners and outsourced to vendors, meaning different skills and processes. Therefore such well known issues still remain in production when customized best practices rules and internal review are not properly defined.
The following list is not exhaustive and is only based on our experience from the field.
Find the complete MSDN post here : http://blogs.msdn.com/b/axinthefield/archive/2014/02/18/top-10-issues-discovered-in-the-dynamics-ax-code-review.aspx
I’ve hear that this request is often asked.
So there is a little piece of code to block all copy of data in a grid (for all form)
If you want to do this only on one form, you need to overwritte the method taks in the form
For my case, you need to select the method “task” on the class “SysSetupFormRun’ and write this:
if (_p1 == #taskCopy)
form = this.control(this.selectedControl().containerId());
if (form && form.handle() == classNum(FormGridControl))
//warning('Cannot copy on this grid!');
ret = super(_p1);
And for disable the copy on a specific field :
In the code I use this : this.selectedControl().containerId()
The method selectedControl return the fields on which we are, so you need simply use this : (with ItemName as fieldName from SalesTable form)
if (_p1 == #taskCopy)
form = this.selectedControl();
if (form.name() == 'ItemName')
//warning('Cannot copy this field!');
My original post : http://blogs.msdn.com/b/sebastien-petre/archive/2013/02/21/blocking-copy-ctrl-c-on-a-grid.aspx
Maybe a lot of you know it but for me, it’s new :-)
You can write some piece of code and want to use syntax highlighting, follow this post :-)
Dynamics Ax Live: How to get rid of the report scaling message the l…: When a report doesn’t fit on a page, depending on it’s properties Ax will resize the report. This is a powerful and very useful feature. No…
AX WONDERS: Deploying Customizations between AX 2012 Environme…: Hi there! I hope everyone is having a good week and that you are ready for another article about AX. In this post, I would like to fo…
They new interface is very FANTASTIC !
Try it now ! http://outlook.com