Skip to main content

Upgrade analysis using Lifecycle Services (LCS) [AX 2012]

The nature of software is that you will have to upgrade or implement at some point. Dynamics AX is no different from any other software system out there. With Microsoft working hard on Lifecycle Services (LCS) site, doing an upgrade analysis has gotten a lot easier. Below is a diagram illustrating the process to produce your analysis report (Excel file).

Below are steps on how to use LCS to produce the upgrade analysis file.

1. Go to LCS site (https://lcs.dynamics.com)

2. Create a new project and click on the Upgrade analysis

2014-05-30_1534_Home

3. Enter the project name and select the AX version. Currently in the list there are 2009 SP1 and AX4SP2.

Before you click on the Create button. Make sure to click on the Download link to download the Rapid Data Collector tool.

2014-05-30_LCS_1

4. Now that you have created your project, go and install the Rapid Data Collector (do not run against your production – take a copy).

5. Install the Rapid Data Collector and it should be a simple executable that you can run.

2014-05-30_RSC_1

6. Once you run it you will get the dialog below. Enter the database server and database name. Accept the agreement and click Collect Data.

This will produce a zip file with the collected stats. Such as table data, usage data, security data. This may take 20minutes for a small one to hours for a large layer.

2014-05-30_RapidDataCollector

6. Now back on LCS follow the wizard from step 3 and upload the *.aod file and the Rapid data collection zip file.

2014-05-30_LCS

7. Click on the Analyse button on the bottom right hand. You can leave it and come back whenever to see it complete.

You should see an excel file that you can download.

2014-05-30_LCS_3

8. The excel file will have details on what objects have been modified.

2014-05-30_1553_001

Stats on affected objects, stats on data usage etc.

2014-05-30_1553

You can use this as the basis of your upgrade estimate. Estimates are always part science and part experience.

Reference:

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

Labels:

Popular posts from this blog

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...
Read more