Update DefaultDimension through Connector for Microsoft Dynamics

We had interesting problem with updating of some data entities' DefaultDimension. Normally for update Connector asks for original data (performs find operation), uses those data as default data and overwrite only those data where values are provided from 3rd party system. It means that any of data defaulted in AX, when create operation was performed, is not overwritten by empty values.

Default Dimensions seem to be just single field of type long instead of dictionary entity in Connector and in VS

There is probably incorrect Extended Data Type on DefaultDimension field in table. There should be DimensionDefault. If there is another one (e.g. RefRecId) then correct code is not generated by AIF wizard to Ax<Table> class and to Data object class.

If you can change EDT then do it and regenerate AxBC classes and data objects.

If you can’t change EDT or regeneration did not help then update classes manually:

Ax<Table> class: 

change EDT in parmDefaultDimension method to "DimensionDefault"

<Service>_<Table> class:

add method createDefaultDimension

public AifDimensionAttributeValueSet createDefaultDimension()

{

    return this.get_NewContainer(#DefaultDimension);

}

change method parmDefaultDimension

public AifDimensionAttributeValueSet parmDefaultDimension(AifDimensionAttributeValueSet _value = null)

{

    if (!prmisDefault(_value))

    {

        this.set_Container(#DefaultDimension, _value);

    }

    return this.get_Container(#DefaultDimension);

}

AX 2012 Integrations - using Microsoft Connector for Dynamics

Although MS Connector for Dynamics' purpose is to connect and integrate products from MS Dynamics family it is possible to use it to integrate AX and 3rd party's systems.

We are currently using Connector this way. I faced several problems through AIF services development to be able to use them with Connector. Here are some points.

AX 2012 R3 Demo running on Azure

I was thinking how to try new release of AX 2012 when the test environment (virtual machine) provided by Microsoft is quite demanding and I have no server with required configuration.
I found this article about how to set up AX 2012 R3 demo on Azure. Hope it will help.

http://blogs.msdn.com/b/axinthefield/archive/2014/05/01/setting-dynamics-ax-2012-r3-demo-with-lcs-and-azure.aspx

Note: You will need acces to Dynamics Lifecycle Services (https://lcs.dynamics.com/) and some Azure subscription.

CRM 2011: "CRM is trying to connect" stuck in Outlook client

WARNING:
Solution of this problem is not included in this article. Unfortunately.

STORY:
Once upon a time I decided that it is the right time to start to play with the MS Dynamics CRM. I've installed new W2003 Server virtual machine, SQL 2005, CRM 4 and MS Office 2003. Everything works nice, web client and outlook CRM client too.

So I tried to create new virtual machine for CRM 2011. I've installed W2008 Server R2, SQL 2008, MS Office 2013 and CRM 2011, applied all SPs. 

The first - clear CRM 2011 (without rollups, I don't know if there is some rollup which supports the Office 2013) doesn't support the Office 2013. So I uninstalled them and installed Office 2003. Everything was fine. 

I started to study some MS course (Introduction to MS Dynamics 2011) and I found out that the Word 2010 should be better for Mail merging. I uninstalled the Office 2003 and installed the Office 2010. Then I uninstalled the CRM client and installed it once more. 

Unfortunately Outlook 2010 crashed with enabled CRM Client add-in. So I uninstalled whole CRM Server and did whole new installation of the CRM Server and the CRM Outlook Client. It didn't help. Outlook was still crashing.

I uninstalled the Office 2010 and installed the Office 2007. Client was reinstalled too. Outlook hadn't crashed anymore but it was unable to connect to the CRM Server. It got stuck on information "CRM is trying to connect". I tried google but there was no useful solution. Nothing worked for me. I thought: Danny, the Office 2003 worked before, try it.

But still it was not possible to connect to the the CRM Server from the Outlook 2003. Still connecting message. Web client worked fine.

Next step was remove that virtual machine. Currently I am installing brand new virtual machine .o)

UPDATE:
I've configured new virtual machine. Order of installation - W2008 Server R2 64bit, Active directory, Office 2010, SQL Server 2008, CRM Server 2011, CRM Client for Outlook. Now it works. It's little freaky.

SUMMARY:
Unfortunately nothing helped me. Only the re-instalation of the whole environment. 

Ax 2012: How to modify SSRS Report design

http://technet.microsoft.com/en-us/library/cc567629.aspx

Ax 2012: Publikování kódu na server

Pokud upravujete kód, který je prováděn na serveru (batch nebo nějaký jiný server job), pak je vždy po úpravě kódu v Ax potřeba kód publikovat do CIL.
Provede se to použitím tlačítka ve vývojovém prostředí

Ax 2012: System.AccessViolationException error

Problem: Ax client crashes when Ax client starts or user clicks on functionality in Ax client.

Symptoms: New code modification was published on AOS but clients have cached old versions.

Solution: Clear *.auc files and User's usage data.

1. Files should be removed from C:/Users/%user%/AppData/Local. Remove all *.auc files.

2. User's usage data can be cleared by user - Ax Client > File > Tools > Options > Usage data > General > Reset.

3. User's usage data can be cleared by admin - Ax Client > System administration > Common > Users > Users > User detail > Options > Usage data > General > Reset

Source:
https://community.dynamics.com/ax/f/33/t/100707.aspx#.Ujv9c8ZT6k8
http://dynamics-ax-live.blogspot.cz/2010/03/more-information-about-auc-file.html

Ax 2009: Debugging of batch jobs

http://msdn.microsoft.com/en-us/library/cc588679(v=ax.50).aspx

Ax 2012: Debugging of server/batch jobs

All batch jobs and service operations now run in managed code (IL) and require different debugging steps.  Rather than setting breakpoints within X++, you need to set them within the IL code that corresponds to the X++ code and debug in Visual Studio.

1. Open Visual Studio as 'administrator' and attach the debugger to the Ax32Serv.exe process.

1. Once done, open up the file you want to debug in Visual Studio. All of the X++ code is compiled into IL and can be found in the following directory after deployment:..\Program Files\Microsoft Dynamics Ax\6.0\Server\AxaptaDev\Bin\XppIL\source\
2. Set a breakpoint in the file you opened.
3. Go to Ax and run the process in batch mode, or execute the service operation. This will end up hitting your breakpoint, provided you set it in the right place.

If you make some changes to X++ code and want those changes reflected in the generated IL code, you need to do the following AFTER you have compiled the X++ code.Once done, your changes will be reflected in your next debugging session.

Source: https://community.dynamics.com/ax/b/mafsarkhan/archive/2011/05/30/how-to-debug-batch-jobs-and-service-operations-in-dynamics-ax-2012.aspx#.UjwULcZT6k8