Dilip's blog on Dynamics 365 for Finance and Operations and Classic AX: February 2008

Tuesday, February 26, 2008

Friday, February 22, 2008

Delete transactional data using SysDatabaseTransDelete class

Got to learn a new thing from my functional buddy:
SysDatabaseTransDelete deletes the transactional data and makes it clean for testing purpose. It retains all the setup and master data. Handy to do regression testing where transactional data has to be deleted and re-tested again.

Using Like in x++ select statement

Use wildcard "*" in select statement
Visit the below link:
http://www.microsoft.com/Businesssolutions/Community/Newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.axapta.programming&lang=en&cr=US

Thursday, February 21, 2008

Worth the Wait: SQL Server 2008

Ten improvements in SQL Server 2008 which is worth the wait

http://www.quest.com/landing/?ID=1252&AdCode=MSSQLTips486x60BannerChangeDirector22008

Wednesday, February 20, 2008

Launch Event of Microsoft Windows Server 2008, Visual Studio 2008 and SQL Server 2008

Please register here.
http://www.microsoft.com/heroeshappenhere/register/default.mspx

I'm lucky to get the confirmation and the event will be on 4th March 2008, Bangalore (Rex Theatre). Will post more about it once I come from there.

Thursday, February 14, 2008

Concept of a new IDE Visual Studio 2010

Amazing!!!
Things to come.....
http://www.codeproject.com/KB/cs/concept_ide.aspx?fid=183427&fr=26#xx0xx

Tuesday, February 12, 2008

Cleared Exam MB6-508 Morphx - Development Introduction

Cleared MB6-508 Morphx - Development Introduction Paper.

The questions revolve around these areas:

General Microsoft AX Architecture – 18%
Understanding of 3-tier Architecture
Understanding of AOS Knowledge of Layer Technology and how to Work with Them Understanding of Label System and Creating Label Files

Development Tools - 18%
General Knowledge of AOT
How to use Intellimorph
How to Import/Export Objects
Debugging Techniquest
Visio

Application Objects– 21%
Creating Data Dictionary Objects
Creating and Working with Forms
Setting Up Projects
Creating and Working with Reports
Creating and Working with Queries
Creating and Working with Menus and Menu Items
Utilizing the Security Structure
Utilizing the Configuration Structure
Table Collections and Virtual Companies

X++ Development – 27%
Data Manipulation/Accessing the Database
Working with Maps
Interacting with the User
Working with Data Models
Working with Class Models
AX-specific
Select Techniques

Best Practices – 16%
Using Naming Conventions
General X++ Coding Standards
Using Validation Techniques

Preparation Materials
Go through the e-learning courses :
8623A_AX40_ENUS_DEVI
8633A_AX40_ENUS_DEVII

https://mbs.microsoft.com/partnersource/communities/training/Certifications/exampreparation/AX4_DevIntro_prep.htm

Microsoft Dynamics Axapta Video 2009

MBS President Krill talks about AX roadmap, Dynamics Axapta 2009 and Governance module

https://mbs.microsoft.com/partnersource/products/axapta/newsevents/news/AXvideo_kirill.htm

Monday, February 4, 2008

Blog on Dynamics Axapta "5.0"

http://blogs.msdn.com/cesardelatorre/archive/tags/Dynamics+AX+_2600_quot_3B00_5.0_2600_quot_3B00_/default.aspx

Getting Started with my first LINQ program

namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{

// The Three Parts of a LINQ Query:

// 1. Data source.
int[] numbers = new int[7] { 0, 1, 2, 3, 4, 5, 6 };

// 2. Query creation.

// numQuery is an IEnumerable
var numquery =
from num in numbers
where (num % 2) == 0
select num;

//3. Query Execution
foreach (int num in numquery)
{
Console.Write("{0,1}", num);
}
}
}
}

Delivering Dynamics AX as Saas (Software as a Service)

http://www.tech2.com/biz/india/news/services/partnership-to-deliver-ms-dynamics-ax-as-a-service/18231/0

LINQ - Language Integrated Query

LINQ is a programming model that introduces queries as a first-class concept into any Microsoft .NET language.

LINQ is a methodology that simplifies and unifies the implementation of any kind of data access. LINQ does not force to use a specific architecture but it facilitates the implementation of several existing architectures for accesing data.

You can download free e-book regarding LINQ from the following site:
http://introducinglinq.com/

Friday, February 1, 2008

Interface must extend interfaces not classes

Got this error when compiling a set of third-party com wrapper classes. Tried compile-forward didn't work.

Solution
Closed and Re-opened AX and then compiled again and the error vanished.

SQL 2005 Database State

The following table defines the database states.

State	Definition
ONLINE	Database is available for access. The primary filegroup is online, although the undo phase of recovery may not have been completed.
OFFLINE	Database is unavailable. A database becomes offline by explicit user action and remains offline until additional user action is taken. For example, the database may be taken offline in order to move a file to a new disk. The database is then brought back online after the move has been completed.
RESTORING	One or more files of the primary filegroup are being restored, or one or more secondary files are being restored offline. The database is unavailable.
RECOVERING	Database is being recovered. The recovering process is a transient state; the database will automatically become online if the recovery succeeds. If the recovery fails, the database will become suspect. The database is unavailable.
RECOVERY PENDING	SQL Server has encountered a resource-related error during recovery. The database is not damaged, but files may be missing or system resource limitations may be preventing it from starting. The database is unavailable. Additional action by the user is required to resolve the error and let the recovery process be completed.
SUSPECT	At least the primary filegroup is suspect and may be damaged. The database cannot be recovered during startup of SQL Server. The database is unavailable. Additional action by the user is required to resolve the problem.
EMERGENCY	User has changed the database and set the status to EMERGENCY. The database is in single-user mode and may be repaired or restored. The database is marked READ_ONLY, logging is disabled, and access is limited to members of the sysadmin fixed server role. EMERGENCY is primarily used for troubleshooting purposes. For example, a database marked as suspect can be set to the EMERGENCY state. This could permit the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state.

Suspect database state

Today, I found one of my AX test database marked as "Suspect" in SQL Management Studio (SQL Server 2005).

I found this link useful:

http://www.sqlusa.com/bestpractices2005/markedsuspect/