Thursday, May 3, 2007

Service Pack 6 for Dynamics Ax 3.0

Hi,

Microsoft has released the service pack 6 for Dynamics Ax 3.0. Click the link below for the downloads

Service Pack 6 for Dynamics Ax 3.0[Requires customer source Logon]

What Makes Microsoft Dynamics AX 3.0 SP6 Important?

Quality and Performance: The service pack will introduce corrections made to solve many
previously reported issues.

The fix lists contain detailed descriptions of improvements

System Requirements:

Microsoft Dynamics AX 3.0 Service Pack 3, 4 or 5 installed. Because the kernel portion of the installation is Microsoft Dynamics Ax 3.0 Kernel Rollup 3, with the base platform of SP3 or later, this affects the installation of SP6.

Installation Notes:

Before you install Microsoft Dynamics AX 3.0 Service Pack 6 it is necessary to read the enclosed readme file in the download package. If you do not follow the correct installation procedure described in the readme file the product may not work properly.

Thursday, April 26, 2007

Microsoft Dynamics Ax 4.0 SP1 Help Update

Hi,

The Help updates for Microsoft Dynamics AX 4.0 SP1 is available under the Link provided below.

Dynamics Ax 4.0 SP1 Help Update[Require Partner source login]

The update contains over 1000 new help topics plus a fix for formatting errors in over 600 topics. This completes the work on all topics displayed through the table of contents as well as help topics for all forms reached through the navigation pane.

Most application and system classes now have information about syntax, run on values, and a list of the class’s methods. Approximately 79,000 reference topics have been updated.
A detailed list of changes made to the MS Dynamics AX 4.0 SP1 Help documentation since December 2006 is also available in the link given above

Wednesday, April 18, 2007

Radio Frequency Identification [RFID]

We are all aware that, Dynamics Ax supports RFID. The Article below will give some basic idea about the RFID.


RFID or Radio Frequency Identification is the Auto-ID technology by which one can identify objects and track information about them wirelessly using radio waves.

In the simplest terms an RFID system consists of a TAG (transponder) and a READER (interrogator). The technology of RFID deals with the remote collection of information stored on a tag using radio frequency communications. Information stored on the tag can range from as little as an identification number, to kilo-bytes of data written to and read from the tag, to dynamic information maintained on the tag, such as temperature histories. The information from the tag/reader combination is either presented to a human operator typically using a
hand-held device or a host computer which automatically manages the information.
Critical performance variables of an RFID system determine the cost of implementation.

Read Range - Range at which communication can be maintained
Memory - Size of the information space contained on the tag
Speed - The rate at which the communication with the tag can take place
Size - The physical size of the tag
Simultaneous read - The ability of the system to "simultaneously" communication with multiple tags
Interference - The reliability of communication with respect to interference due to material in the path between the reader and the tag
Accuracy - Read success rate especially in presence of many tags
Life & Re-use - Tags should be robust to handle harsh temperatures and environments. Battery life limits life of tag.

Several factors determine the level of performance that can be achieved in these variables.
Legal/regulatory emission levels allowed in the country of use. Battery is included in the tag to assist its communication or not. Frequency of the RF carrier used to transport the information.

The main components involved are:

RFID tags - attached on objects to identified and contain information
RFID readers - generates and RF signal to identify RFID tags
Antennae - Carries the RF signal to identify tags
Aggregation Software - Collects the required data

RFID Middleware
Filter the enormous data and convert it into information.
Integration with backend business systems (ERP, CRM, WMS, SCM etc.)

RFID Components
RFID Tags
RFID tags are attached on objects, to identify them and can store information. Tags are classified based on their characteristics.

Active and Passive tags

Active tags use a battery to power its chip, Passive tags use the energy of the RF signal from readers.

Frequencies

Low Frequency (LF) – 125 KHz
High Frequency (HF) – 13.56 MHz
Ultra High Frequency (UHF) – 433 to 960 MHz – region specific
Microwave – 2.4 to 5 GHz Dual Frequency (DF) – power up at 125 KHz & Backscatter at 6.8 MHz

Read/Write capability

Read Only
Write Once Read Many
Write Many Read Many
Tag/Reader Communication Protocols

Reader talks first
Tag talks first
RFID Readers
RFID readers consist of a transmitter, receiver, antennae and a decoder. They communicate with RFID tags, identify them and retrieve data stored on the tag. Different types of RFID readers:
Fixed readers - Entry/Exit, Conveyer etc
Mobile readers - handheld readers, forklift readers etc
Dual Barcode and RFID readers

RFID Antennae

Apart from the antennae that is present in a tag an antennae is required between the reader and a tag to enable communication. The antennae can either be built in to the reader or it can be a powerful external antenna that can enhance the read range and quality of RF communication.
Most real scenarios require external antennae to direct the RF signal and provide comprehensive coverage of the area.

RFID Middleware

RFID Middleware is an intelligent toolset of software modules that transforms real-time data collected by RFID hardware into relevant operational information for instant and informed decision making.

Functions of Middleware

Filter the huge data collection and transform into relevant information
Seamless integration with existing Business Systems
ERP
CRM
WMS / SCM
Departure Control Systems
Workshop Management Systems
Others
Specify the required information to be collected from the RFID environment
Effectively manage data network infrastructure based on defined business logic
Ease scalability of RFID application

RFID vs. BARCODES

Durable – Can withstand harsh temperatures & environments
Line of sight – Not required unlike barcode technology
Orientation – Not required unlike barcode technology
Simultaneously Read Many Tags – possible using anti-collision algorithms
Read range – Much Longer than barcodes
Tamper security – RFID tags have a Unique Permanent Serial Code that cannot be duplicated.
Reading Speed – Faster than barcodes
Memory – Can store useful data with dynamic update
Cost Effective – RFID tags maybe more expensive than barcode labels. But they have many advantages over barcode labels. Therefore RFID could be more cost effective provided it is used in the right manner and for the right application.

Microsoft Sure Step Methodology

Microsoft Dynamics Sure Step provides a complete methodology—including project management discipline and field-tested best practices—plus user-friendly tools that enable you to more successfully deploy, migrate, configure, and upgrade Microsoft Dynamics AX, Microsoft Dynamics CRM, Microsoft Dynamics GP, Microsoft Dynamics NAV and Microsoft Dynamics SL.

For more information click the link below

Microsoft Sure Step[Requires partner source login]

Thursday, April 12, 2007

How to modify the behavior of dialog boxes to enable forms to appear in full-screen mode in Microsoft Dynamics AX

This article describes how to modify the behavior of dialog boxes to enable forms to open in full-screen mode. You can apply this modification to a specific dialog box or to all dialog boxes.

Click the link to download[requires partner source login]

Wednesday, April 11, 2007

What's New in Dynamics Ax 4.0 AOS?

The Application Object Server (AOS) provides the infrastructure to execute the business logic on the middle tier of a 3-tier Microsoft Dynamics AX installation. The AOS handles the connectivity, security, and database connection management that an Microsoft Dynamics AX system requires.

In Microsoft Axapta 3.0, the AOS was a standalone program, that is, an executable file that was started and stopped by the Microsoft Dynamics AX Server Manager, which functioned as a load-balancing application. In Microsoft Dynamics AX, the AOS is implemented as a Microsoft Windows Service to take advantage of the following:

· Windows Service applications run in the security context of a specific user account that is different from a user that is logged on or the default computer account. After installation of Microsoft Dynamics AX, the default user account has all the permissions required to access Microsoft Dynamics AX functionality.
· Eliminating the dependency on the Microsoft Dynamics AX Server Manager removes a security threat by which an attacker could send a command to the AOS to shut it down.
· A Windows Service application runs in its own Windows Session and takes advantage of the Service Control Manager (a feature of the Windows Server 2003 operating system) to maintain status information and to provide the user interface for managing the AOS.
· Windows Services can be configured to start at system startup or upon demand, and they continue to run even when no user is logged into the system.
· Server status can be reported to the Windows event log, allowing administrators to view errors and warnings that can aid in troubleshooting problems.

Upgrade from Ax 3.0 to Ax 4.0

Hi,
Before doing the upgrade, Please have a look on the link below[Requires partner source login]. The link will provide the entire detail about the upgrade. The link will be updated periodically.Hope it will be useful when we are doing upgrades.


https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={863D51CC-3127-4E83-94A7-AE95CE9E660D}&NRORIGINALURL=/partnersource/resources/support/selfsupport/hottopics/axapta/ax30to40upgrade.htm?printpage=false&NRCACHEHINT=Guest&printpage=false&wa=wsignin1.0

How to do the setup for Version Control System in Ax 4.0

Hi,
We all aware that Microsoft Dynamics Ax 4.0 provides the version control facility for proctecting our valuable customizations. Check out the link below[Requires partner source login] to know how to do the setup for Version Control system.


https://mbs.microsoft.com/partnersource/documentation/whitepapers/ax40_version_control_setup.htm?printpage=false

Thursday, April 5, 2007

How to Setup Alerts in Dynamics Ax 4.0

INTRODUCTION

This article describes how to set up Business Alerts in Microsoft Dynamics AX 4.0. This article also describes how to set the e-mail address from which Business Alert e-mail messages are sent.

MORE INFORMATION

Configure a user account to receive alerts

To configure a user account to receive alerts, follow these steps:
1. In the Navigation Pane, click Administration, and then click Users.
2. Select a user, and then click User Options.
3. Verify that the e-mail address where you want the user to receive alerts is in the E-mail field.
4. In the Receive alerts every (minutes) box, type 1.
5. In the Pop-up link destination list, click To alert.
6. In the Send alert as e-mail message list, click Define on each alert rule.
7. In the Show pop-ups list, click Define on each alert rule, and then click Apply.
8. Close the Options window.

Add the "E-mail distributor batch" job

The "E-mail distributor batch" job is the batch job that monitors and sends e-mail messages. To add the "E-mail distributor" batch job, follow these steps:
1. In the Navigation Pane, click Administration, expand Periodic, expand E-mail processing, and then click Batch.
2. In the "E-mail distributor batch" window, click Recurrence.
3. In the Recurrence window, click No end date.
4. Click Minutes.
5. In the Count box, type 1, and then click OK.
6. In the "E-mail distributor batch" window, click to select the Batch processing check box, and then click OK.Note You receive an Infolog message that resembles the following message:
Information: The E-mail distributor batch job is added to the batch queue.
7. Click Close to close the Infolog dialog box.
8. On the Tools menu, click Development tools, and then click Application Hierarchy Tree.
9. Expand Forms, and then double-click Tutorial_EventProcessor.
10. On the Tutorial_EventProcessor form, click Start, and then verify that the status is In waiting.

Set up a new alert rule

Alert rules define when alerts are sent and how they are received. To set up a new alert rule, follow these steps:
1. In the Navigation Pane, click General ledger, and then click Chart of accounts.
2. On the Overview tab, right-click a cell in the Account name column, and then click Create alert rule.
3. In the Alert me when area, select the field that you want to monitor with this alert rule in the Field list. For example, select Account name.
4. In the Event list, select the event that you want to trigger an alert. For example, select has changed.
5. In the Alert me for area, select the All records in Ledger chart of accounts option.
6. In the Alert me until area, select the No end date option.
7. In the Alert who area, select the user account that you want to receive this alert in the User ID list.
8. In the Also alert me by area, click to select the Show pop-ups check box.
9. Click to select the Send e-mail check box, and then click OK.
10. Close the "Manage alert rules" window.

Test the alert

To test the alert that you have set up, follow these steps:
1. In the Navigation Pane, click General ledger, and then click Chart of accounts.
2. On the Overview tab, change the name of the account for which you set up a new alert.
3. In the Navigation Pane, click Administration, click Periodic, click E-mail processing, and then click E-mail sending status.
4. The "E-mail sending status" window shows e-mail alerts that have been sent.

Set the e-mail address from which alerts are sent

You can set the e-mail address from which alerts are sent by selecting an e-mail template. To do this, follow these steps:
1. In the Navigation Pane, click Basic, click Alerts, and then click Alert parameters.
2. In the E-mail ID list, select the e-mail template from which you want e-mail alerts to be sent.

New Application Patching Strategy for Microsoft Dynamics AX 4.0 SP1

The process for developing, building, and releasing application hot fixes and updates will fundamentally change from Microsoft Dynamics AX 4.0 SP1 onwards.
The hot fix layer files will be made cumulative in the sense that previous fixes will be included in the latest released hot fix or the next critical update. Due to this cumulative approach, released hot fixes are expected to be tested in conjunction with all supported updates and their fixes. In this way, we intend to reduce conflicts between fixes.
Another major difference between the patching strategy of Microsoft Dynamics AX 3.0 and 4.0 SP1 onwards, will be the type of hot fix deliverable. We expect to release cumulative hot fixes as an AOD file, which will be distributed out of the DIS layer inside Microsoft Dynamics AX. This should make it simpler to distinguish Microsoft code from code developed by a partner, as well as making it possible to use the inbuilt upgrade tools to upgrade a partner’s customization layer(s) in a similar manner to installing a service pack in Microsoft Dynamics AX 3.0. A major advantage of this new approach is that it will now be easier for Microsoft as well as partners to better determine the current hot fix status of any customer system.
We expect that all cumulative hot fixes will be rolled forward into the next critical update and major release, so that partners upgrading their customers to a new major release should only need to delete the entire DIS layer to help ensure a smoother upgrade path.

Dynamics Ax 4.0 Database upgrade for Oracle

Before starting the upgrade process do the following activities:

Create an empty Oracle 10g database. Microsoft dynamics will support Oracle 10g database only. While creating the database log in as an Windows Administrator
Use the following SQL statement for creating new user in Oracle 10g

CREATE USER "OPS$\" IDENTIFIED EXTERNALLY;
Grant rights to the user "OPS$\" as given below :
GRANT ALL PRIVILEGES, SELECT ANY DICTIONARY TO “OPS$\";
For upgrading the existing database, create the tablespace in Oracle 10g with the same name as in oracle 9. For New Installation create 3 tablespaces (AXTAB,AXIDX,AXTMP) as given below:

CREATE TABLESPACE AXTAB DATAFILE'D:\ORACLE\ORADATA\AXDB\AXTAB01.DBF' SIZE 3000M BLOCKSIZE 8192;CREATE TABLESPACE AXIDX DATAFILE'D:\ORACLE\ORADATA\AXDB\AXIDX01.DBF' SIZE 2000M BLOCKSIZE 8192;CREATE TEMPORARY TABLESPACE AXTMP TEMPFILE'D:\ORACLE\ORADATA\AXDB\AXTMP01.DBF' SIZE 1000M;COMMIT;
4.1. Create a schema with the name DBO.

There are two xpo files that need to be imported into your 3.0 client and run against the old 9i database as per steps below:

Import PrivateProject_UpgradeColumnList.xpo from the SP1 DatabaseUpgrade folder into your 3.0 system a. Open the form UpgradeColumnList from the imported project b. Click on the button Generate tables UPGRADECOLUMNS and UPGRADETABLES are created in your 3.0 db. They contain fields that need to be updated from int to int64


To trim the right justified fields: Import PrivateProject_LeftJustified.xpo from the SP1 DatabaseUpgrade folder into your 3.0 system c. Run the job MainJob from the imported project opens a form d. Click “Left justify all” and wait until it’s done

If you are running a Oracle version for Windows, It is recommended running the DB Upgrade tool on the same machine where Oracle 10g is installed using the Administrator account.

On the machine where you are running the DB upgrade tool, verify if you can connect to the Oracle 9 by testing it using the ODBC wizard. This is to make sure that there is no problem accessing the Oracle 9 database from that machine.

After completing the above steps, run the DB upgrade tool from the Dynamics 4.0 DVD. The explanation of the fields available in the oracle tab is given below

Source

· Source connect string: Type connection information for the source database (Oracle 9) in the format Server Name/SID.
· Schema owner: Type the name of the schema under which the database objects were created.
· User Name: Type the name of a user who has access to the source database.
· Password: Type the password of a user who has access to the source server.
Target

· Target connect string: Type connection information for the target database, where the new, preliminary Microsoft Dynamics AX database is stored, in the format Server Name/SID
· Use this schema: Type the schema name (DBO by default) for the new, preliminary Microsoft Dynamics AX database