A practitioner’s musings on Dynamics 365 Finance and Operations
There are a lot of frameworks in Dynamics Ax 2012 a Few of them listed as follow.
Above picture is taken from following link
http://blogs.msdn.com/b/microsoft_press/archive/2012/10/25/new-book-inside-microsoft-dynamics-ax-2012.aspx
Role center is user page; appear on opening at Dynamics Ax. The role center is depending on rights and role of user. Role center provide dashboards, which helps to user to monitor their roles. This information includes transaction data, alerts, links and common tasks that are associated with user’s role.
Another example of Role center:
Area Page. Area page is the main page of Every Module.
Every area page have link to, List page, Journal, Reports, Setup table list, Inquiries and Periodic page.
Common or list pages. These links leads you to list page of any Entities in that module. For example in Account receivable module contains customer list page. Through list page user is able to Navigate every part of data related to that entity.
Detail From: Detail forms are primary way to create or update entities in Dynamics Ax like customer Vendor, worker and products. These detail forms can be open by click on list page. By default these pages are open in read only mode. You have to click edit button to open in detail page.
Transaction detail Forms.
Transaction detail forms are forms that are used to create, update transaction in Microsoft Dynamics Ax.
Traction is business event that occurs with in company that needs to be recorded in ERP system.
Transaction detail forms have to divided two parts one is Line view and Header view.
: This shows a few header level fields which are required for transaction. This default view and items are added here.
Header View:
This contains all most all fields at header view. Most of fields have default values and required to modify here.
Journal: These pages link to all related which have some functional or finance related information.
Periodic:
All those page which will periodically access by user example
Payment fee.
The setup contoso demo data for Dynamics Ax 2012 R3 is different from previous version. I remember, I used .dat file to load demo data into Dynamics Ax 2012 R2. Now DynamicsAX2012R3DemoData.exe available partner Resource.
DynamicsAX2012R3DemoData.exe extracted files round 15 GB. Extracted folder contains three types of files. According to MSDN
Installation of Test Data Transfer Tool:
The MSDN Described The Import export with Test Data Transfer Tool (beta) as follow.
Test Data transfer Tool is available on partner resource.
Go on following link
On login I found download page
There will be zip file downloaded. On running I found following installation wizard.
Setup run will be generated as following
Import Data Into Dynamics Ax 2012 R3 instance:
And import MetaDataXMLGenerator.xpo in dynamics Ax.
This xpo imports results a job inside job node under AOT.
This job will generate Metadata.xml. This Metadata.xml will be created in window temporary folder.
Path of file in metadata.xml can be get from infobox which will appear after successful run of job.
if you lost infobox,You can get temporary folder path with following command echo %temp%. where you can get Metadata.xml
Copied metadata.xml into [list] folder of test tool Data folder. If it already exists then overwrite it.
Go to services, and stop the Dynamics Ax service.
Now open command prompt. Go to directory where Test import tool is extracted.
Run the following command
DP.exe IMPORT “E:\Contoso_Demo_Data\DynamicsAXR3DemoData” MicrosoftDynamicsAx
If your SQL server configure with other than default instance then you must mentioned the server with instance name for example
DP.exe IMPORT “E:\Contoso_Demo_Data\DynamicsAXR3DemoData” MicrosoftDynamicsAx WIN-TLRNMFCLU9N\SQLSERVER
Please update path according to your installation.
After running the command, you will find following window which describe the process by remaining table to number data, and number of error occurs during import.
This process takes hours and hours with respect to your machine. After completion, I found demo data inside my dynamics Ax 2012 R3.
I found following log entry in event log,
Unable to write the generated WCF configuration to local storage. The generated WCF configuration will be used from memory. The contents of the new configuration are written to the following temp file: C:\Users\i<BC Account> \AppData\Local\Temp\Microsoft.Dynamics.AX.Framework.Services.Client.Configuration.ClientConfigurationInternal.log.
Exception details:
System.ComponentModel.Win32Exception (0x80004005): Access is denied
at Microsoft.Dynamics.AX.Framework.Client.ConfigurationModel.NativeRegistry.OpenNativeRegistryKey(String keyPath, Boolean writable)
at Microsoft.Dynamics.AX.Framework.Client.ConfigurationModel.MachineWideRegistryConfigurationModel.GetConfigurationKey(Boolean writable)
at Microsoft.Dynamics.AX.Framework.Client.ConfigurationModel.RegistryConfigurationModel.WriteWcfConfiguration(String configuration, Guid versionId)
at Microsoft.Dynamics.AX.Framework.Services.Client.Configuration.ClientConfigurationInternal.GetClientConfiguration()
All servers configured to use local configurations stored in the registry.
Possible solution:
As a side note, this is another example of undocumented requirements, and in my mind something the installer should configure during installation or at least describe as a manual configuration item.
Apparently the Business Connector binary (assembly) has built in functionality to automatically refresh the WCF configuration part of the AX configuration requiring additional configuration steps to be performed.
Update: http://ax2012tech.blogspot.com/2014/01/ax-2012-unable-to-write-generated-wcf.html
This could also be caused by Group Policy (domain) settings applied after the AX Components were installed.
reference:
reference
|
Table Name
|
Table Description
|
|
SalesTable
|
The SalesTable table contains all sales order headers regardless of whether they have been posted.
|
|
SalesLine
|
The SalesLine table contains all sales order lines regardless of whether they have been posted.
|
|
InventDim
|
The InventDim table contains values for inventory dimensions.
|
|
static void SalesOrdersXppImport(Args _args)
{
#define.Customer(“US-001”)
#define.DeliveryDate(“1/1/2014”)
#define.ItemId(“M0001”)
#define.Qty(10)
#define.Unit(“ea”)
SalesTable salesTable;
SalesLine salesLine;
InventDim inventDim;
try
{
ttsbegin;
//Order header
salesTable.clear();
salesTable.initValue(SalesType::Sales);
salesTable.SalesId = NumberSeq::newGetNum(SalesParameters::numRefSalesId()).num();
salesTable.DeliveryDate = str2Date(#DeliveryDate, 213);
salesTable.CustAccount = #Customer;
salesTable.initFromCustTable();
if (salesTable.validateWrite())
{
salesTable.insert();
//Order line
inventDim.clear();
inventDim.InventSiteId = “1”;
inventDim.InventLocationId = “12”;
salesLine.clear();
salesLine.initValue(salesTable.SalesType);
salesLine.initFromSalesTable(salesTable);
salesLine.ItemId = #ItemId;
salesLine.initFromInventTable(InventTable::find(#ItemId));
salesLine.InventDimId = InventDim::findOrCreate(inventDim).inventDimId;
salesLine.SalesQty = #Qty;
salesLine.RemainSalesPhysical = salesLine.SalesQty;
salesLine.SalesUnit = #Unit;
salesLine.QtyOrdered = salesLine.calcQtyOrdered();
salesLine.RemainInventPhysical = salesLine.QtyOrdered;
salesLine.setPriceDisc(InventDim::find(salesLine.InventDimId));
if (salesLine.validateWrite())
{
salesLine.insert();
}
else
throw error(“Order line”);
}
else
throw error(“Order header”);
ttscommit;
}
catch
{
error(“Error!”);
return;
}
info(“Done!”);
}
|
Recently I found the training session for new features of dynamics Ax 2012 R3 on Channel 9 website.
The important features of Dynamics Ax 2012 R3 are Warehouse management and Transportation management. Presenters described these feature in brief and very precisely. You can explore these features on below link of Channel 9.
http://channel9.msdn.com/Series/Microsoft-Dynamics-AX-2012-R3-Training
I just saw the R3 demo VM. There is Lot of new features. The major feature Include
Let’s see small detail which I just collected.
Retail
For developer or technical point of
References:
Here are some reference and articles I found
A great article about compiler enhancement in Dynamics Ax 2012 R3 http://axwonders.blogspot.com/2014/03/hi-there-i-hope-everybody-is-doing.html
A detail article about Project management functionality enhancement in Dynamics Ax 2012 R3
http://sandeepchaudhury.wordpress.com/2014/01/26/enhancements-to-project-planning-functionality-in-ax-2012-r2-cu7/
There is registration going on for Webinar for Dynamics Ax 2012 R3 visit following link
https://presentations.inxpo.com/Shows/microsoft/4-10-14/Registration/Registration.html?AffiliateKey=21572&AffiliateData=
References : http://www.mwdata.dk/news/new-exciting-features-for-dynamics-ax-2012-coming-up/
http://blogs.msdn.com/b/dax/archive/2013/11/05/microsoft-dynamics-ax-2012-r3-a-preview.aspx
http://blog.encorebusiness.com/new-features-microsoft-dynamics-ax-2012-r3/
http://blog.encorebusiness.com/new-features-microsoft-dynamics-ax-2012-r3/
The SSRS reports need a data source from where data can be fetched and displayed on the report. Since we are going to develop query based report therefore we will use an AOT query as a data source.
For creating report, First we have to create A AOT Query. For this we have A simple AOT query base on Bank Deposit table
BankDeposit table.
By Default there is no field selected under field.
Click on it and set dynamic property to ‘YES’, so all possible filed will appear on table.
You can see all the fields of the table.
Now open Visual studio and create a new SSRS report named it as QueryBasedReport. Use this query as data source
Now you need to create a data set, QueryBasedReportDS, that will refer to an AOT query created earlier. In data set properties set ‘Data Source Type’ to ‘Query’ and in query property select the AOT query SampleQuery created earlier.
All the fields are visible under Fields node of QueryBasedReportDS. These fields won’t be visible if you haven’t set ‘Dynamic’ property of Fields to ‘Yes’ in AOT query and you won’t be able to see any field on report. Now add an auto design by right clicking on Design node and name it Report. Drag the data set of your report “QueryBasedReportDS” to report design named ‘Report’.
Make sure that the table you are using has some records in it. If there is data in table and still you are unable to see records on report, you might need to do following steps. Go to ‘Parameters’ node of your report ‘QueryBasedReport’.Right click on AX_ComapnyName and select properties. Set the value of the property ‘Visibility’ from Hidden to Visible and save the changes.Now right click on report design to preview it. Following dialog will appear. Enter AX_CompanyName ‘CEU’.
Now click on Report tab. Following report output will be shown.You can also view the developed report from browser using following url http://localhost/reports but before this you need to deploy the report on report sever. This can be done by right clicking the solution in
visual studio and selecting deploy. default.
If this service is not started, start it. If it is already started, you need to restart it. After restarting the service, go to visual studio and deploy the solution. Your report is successfully deployed on the server.
Now you can see the report result from any browser. Go to http://localhost/Reports click on DynamicsAX folder and click on the report you want to run. In our case, it is QueryBasedReport.Report. If you can’t find any record, change the company name from DAT to CEU.
Now you can see data on the report.
Running report Inside Dynamics AX Client, you have to output menu item. Save following properties and save the changes.
You will see records on the report.
So these were the errors and solutions, I came across so far. I hope it helps. If you have encountered some more, please do share. Keep rocking 🙂
Here is the code in X++:
public static void CustomerForm(Args _args)
{
//Initialization
DictTable dictTable;
DictTable dictTable1;
Form form;
FormBuildDesign design;
FormBuildDataSource formBuildDataSource;
FormBuildDataSource formBuildDataSource1;
FormBuildActionPaneControl actionPane;
FormBuildActionPaneTabControl actionPaneTab;
FormBuildButtonGroupControl buttonGroup1;
FormBuildButtonGroupControl buttonGroup2;
FormBuildCommandButtonControl CommandNew;
FormBuildCommandButtonControl CommandDelete;
FormBuildMenuButtonControl CustomerButton;
FormBuildFunctionButtonControl NewCustomerButton;
FormBuildFunctionButtonControl ForecastButton;
FormBuildGroupControl Grp;
FormBuildGridControl grid;
FormBuildGroupControl grpBody;
Args args;
FormRun formRun;
#task
//Adding DataSources
dictTable1 = new DictTable(tableNum(CustTable));
dictTable = new DictTable(tableNum(DirPartyTable));
form = new Form();
form.name(“Customer Overview”);
formBuildDataSource = form.addDataSource(dictTable.name());
formBuildDataSource.table(dictTable.id());
formBuildDataSource1 = form.addDataSource(dictTable1.name());
formBuildDataSource1.table(dictTable1.id());
//Building Form Design
design = form.addDesign(‘Design’);
design.caption(“Overview”);
design.style(FormStyle::SimpleList);
design.titleDatasource(formBuildDataSource.id());
//Adding Action Pane and Buttons
actionPane = design.addControl(
FormControlType::ActionPane, ‘ActionPane’);
actionPane.style(ActionPaneStyle::Strip);
actionPaneTab = actionPane.addControl(FormControlType::ActionPaneTab, ‘ActionPaneTab’);
buttonGroup1 = actionPaneTab.addControl(FormControlType::ButtonGroup, ‘NewDeleteGroup’);
buttonGroup2 = actionPaneTab.addControl(FormControlType::ButtonGroup, ‘ButtonGroup’);
CommandNew = buttonGroup1.addControl(FormControlType::CommandButton, ‘NewButton’);
CommandNew.buttonDisplay(FormButtonDisplay::TextAndImageLeft);
CommandNew.normalImage(’11045′);
CommandNew.imageLocation(SysImageLocation::EmbeddedResource);
CommandNew.primary(NoYes::Yes);
CommandNew.command(#taskNew);
CommandDelete = buttonGroup1.addControl(FormControlType::CommandButton, ‘NewButton’);
CommandDelete.text(“Delete”);
CommandDelete.buttonDisplay(FormButtonDisplay::TextAndImageLeft);
CommandDelete.normalImage(’10121′);
CommandDelete.imageLocation(SysImageLocation::EmbeddedResource);
CommandDelete.saveRecord(NoYes::Yes);
CommandDelete.primary(NoYes::Yes);
CommandDelete.command(#taskDeleteRecord);
CustomerButton = buttonGroup2.addControl(FormControlType::MenuButton, ‘CustomerquickCreate’);
CustomerButton.helpText(“Create New Customer”);
CustomerButton.text(“Customer”);
NewCustomerButton = CustomerButton.addControl(FormControlType::MenuFunctionButton, ‘CustomerquickCreate’);
NewCustomerButton.text(‘New’);
NewCustomerButton.saveRecord(NoYes::No);
NewCustomerButton.dataSource(formBuildDataSource.id());
NewCustomerButton.menuItemName(menuitemDisplayStr(CustomerquickCreate));
ForecastButton = buttonGroup2.addControl(FormControlType::MenuFunctionButton, ‘SalesForecast’);
ForecastButton.text(‘Forecast’);
ForecastButton.saveRecord(NoYes::No);
ForecastButton.menuItemName(menuitemDisplayStr(ForecastSalesGroup));
//Body
grpBody = design.addControl(FormControlType::Group, ‘Body’);
grpBody.heightMode(FormHeight::ColumnHeight);
grpBody.columnspace(0);
grpBody.style(GroupStyle::BorderlessGridContainer);
grid = grpBody.addControl(FormControlType::Grid, “Grid”);
grid.dataSource(formBuildDataSource.name());
grid.widthMode(FormWidth::ColumnWidth);
grid.heightMode(FormHeight::ColumnHeight);
grid.addDataField(formBuildDataSource.id(), fieldNum(DirPartyTable,Name));
grid.addDataField(formBuildDataSource1.id(), fieldNum(CustTable,AccountNum));
grid.addDataField(formBuildDataSource.id(), fieldNum(DirPartyTable,LanguageId));
Grp = design.addControl(FormControlType::Group, ‘Group’);
ForecastButton = Grp.addControl(FormControlType::MenuFunctionButton, ‘SalesForecast’);
ForecastButton.text(‘Forecast’);
ForecastButton.menuItemName(menuitemDisplayStr(ForecastSalesGroup));
args = new Args();
args.object(form);
formRun = classFactory.formRunClass(args);
formRun.init();
formRun.run();
formRun.detach();
}
