Recently while developing a WCF Service for AX Employee Data, came across this particular
Error:
Type 'System.Xml.XmlDocument' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members you want serialized with the DataMemberAttribute attribute.
Resolution:
Put xmlserializerformat just above your datamethod in your interface class.
[OperationContract]
[XmlSerializerFormat]
XmlDocument GetEmployees();
Thursday, October 16, 2008
Dynamics AX 2009 Snap
Availability of DAX 2009 Snap to Download from the following link:
http://www.codeplex.com/axsnap/Release/ProjectReleases.aspx?ReleaseId=18334
Offline Expense - This snap-in enables expenses to be entered in Excel while disconnected from the corporate network, and then posted to Dynamics AX at a later time. This snap-in uses WCF-based services and LINQ to retrieve data from Dynamics AX, and uses the Application Integration Framework, or AIF to send business documents to Dynamics AX.
Business Data Lookup (BDL) - This snap-in enables information workers to access data from Dynamics AX from within Excel, Word and Outlook. This snap-in is an upgrade of the BDL snap-in that was distributed with Microsoft Dynamics AX 4.0. These applications require .Net 3.5, Microsoft Office 2007, Microsoft Visual Studio 2008 and Microsoft Dynamics AX 2009. Each snap-in contains a document describing the basic architecture, functional footprint, and deployment steps for exploring the sample code.
http://www.codeplex.com/axsnap/Release/ProjectReleases.aspx?ReleaseId=18334
Offline Expense - This snap-in enables expenses to be entered in Excel while disconnected from the corporate network, and then posted to Dynamics AX at a later time. This snap-in uses WCF-based services and LINQ to retrieve data from Dynamics AX, and uses the Application Integration Framework, or AIF to send business documents to Dynamics AX.
Business Data Lookup (BDL) - This snap-in enables information workers to access data from Dynamics AX from within Excel, Word and Outlook. This snap-in is an upgrade of the BDL snap-in that was distributed with Microsoft Dynamics AX 4.0. These applications require .Net 3.5, Microsoft Office 2007, Microsoft Visual Studio 2008 and Microsoft Dynamics AX 2009. Each snap-in contains a document describing the basic architecture, functional footprint, and deployment steps for exploring the sample code.
Wednesday, September 24, 2008
DAX 2009 and a brief note on Version Control
This is regarding AX development environment setup for different version control options which is bundled with DAX 2009.
Dynamics AX 2009 IDE can be integrated with any of the following version control systems:
A. MorphX Version Control System (VCS)
i. Out of box version control integration available with DAX 2009
ii. Developers can use shared AOS
iii. No need of Team Server *
B. Visual Source Safe (VSS) OR Team Foundation Server (TFS)
i. Local copy of AOT stored on each developer computer in repository folder
ii. Each developer machine needs to have AOS and database server (So, we need to have a Windows 2003 Server for each developer since AOS installation’s pre-requisite is Windows Server 2003)
iii. Additional server for installing VSS/TFS Server
iv. * Team Server is required
*Team Server also known as Team ID Server issues ID’s to AOT objects to make sure that all ID’s are unique when we work under version control. Team Server is a required when we use VSS/TFS as our Version Control System.
We need to evaluate our version control requirements for our projects based on the above info. What I feel is integrating with VSS/TFS would be a costly affair (considering the server requirements) but the benefits which we get is a proper build process in place. On the other hand, using the internal Morphx VCS, we get the benefit of a shared AOS but we won’t be having a proper build management. For e.g. suppose AX Crashes then the VCS is also gone with it.
Dynamics AX 2009 IDE can be integrated with any of the following version control systems:
A. MorphX Version Control System (VCS)
i. Out of box version control integration available with DAX 2009
ii. Developers can use shared AOS
iii. No need of Team Server *
B. Visual Source Safe (VSS) OR Team Foundation Server (TFS)
i. Local copy of AOT stored on each developer computer in repository folder
ii. Each developer machine needs to have AOS and database server (So, we need to have a Windows 2003 Server for each developer since AOS installation’s pre-requisite is Windows Server 2003)
iii. Additional server for installing VSS/TFS Server
iv. * Team Server is required
*Team Server also known as Team ID Server issues ID’s to AOT objects to make sure that all ID’s are unique when we work under version control. Team Server is a required when we use VSS/TFS as our Version Control System.
We need to evaluate our version control requirements for our projects based on the above info. What I feel is integrating with VSS/TFS would be a costly affair (considering the server requirements) but the benefits which we get is a proper build process in place. On the other hand, using the internal Morphx VCS, we get the benefit of a shared AOS but we won’t be having a proper build management. For e.g. suppose AX Crashes then the VCS is also gone with it.
Tuesday, September 16, 2008
Sunday, September 14, 2008
DAX 2009, WCF Service and Windows Mobile
I was working on a small POC which consumes a WCF Service to update DAX 2009 Employee data.
This WCF Service in-turn consumes a legacy ASMX Service to talk to a different application and loads the data from that webservice. And, later the data is updated to DAX 2009.
These are the 2 steps:
Step A: Windows Mobile Loads the data from a WCF Service which in turn invokes the Business Logic Layer which calls the Data Access Layer (this layer consumes the legacy asmx webservice of the external app)
STEP B: Updates Data to AX 2009
Subscribe to:
Posts (Atom)