What’s New in AX 7.0
What’s new in Technologies?
•Low latency between logical control and AOS,
•High latency between physical control and logical control
•All X++ runs on server tier,
•Form app state on server,
•Deltas keep control state in sync,
•Web server to support WAN usage
•Single Page Application,
•Common browser actions for new windows/tabs,
•Back button for all forms and panels
•Simplifying navigation and form management
•URL updating for direct navigation items
•Parent record context
What new in basic functionalities?
•Fully web base function (setup /configurations/operation/reporting)
•Very colourful web base client with new slider functionality
•New Fleet management module coming in
•New task recorder function has been introduce, which you can play from AX and it will guide you the all the steps in AX itself.
•Workflow ribbon has been removing, workflow operationally has been changed. But configuration of the workflow is same like AX2012 R3 CU9.Optional workflow on all create/edit processes.
•EP/ESS has been remove, its replace via ESS/MSS workspaces
•Error messaging or warning messaging look change like LCS.
•Lots of reports layout changed with nice look and fill which can be used as external business documents.
What new in module specific functionalities?
•Financial statement reports now migrated to management report. There is no standard financial statement report available via SSRS reporting. Deployed Management reporter with AX 7.0, it means you no need to install separately.
•There are new 16 default reports available for General ledger module.
•Few navigation in GL form got changed i.e., legal entity of the main account move to as a fast tab in main account form.
•Budget planning has enhanced, now it’s more easy to use for user and as well as consultant to configure.
•Mis Charges posted in Product receipt has introduced in AX 7.0
•Human resource management now more easy to market due to web capability. Now it’s can complete with other HRMS specific product.
•Employee master is very easy to create.
•New workflow has been in introduce for loan equipment request via ESS workspace.
•Expenses management module is now support calendar view expenses report preparation with itemized capability.
•Project Accounting module has few new changes; role base estimation which has introduced in workforce scheduling. It’s also integrated with WBS of a project. Its support role base operation, automatic team generations
•Pricing for the role also introduced, which help the sales team and project team do a cost & revenue analysis with role.
•WBS template export and import function introduced, which help the project manager use this function without MS project server 2013 integrations
•360 degree view available for resource available with graphical view. Resource load visibility also available from the same view.
AX 2012 SSRS Report: Multiple design under Print management
If new formats for Sales order confirmation/Picking/Packing/Invoice Purchase order postings etc. are needs to be added. Following steps needs to be performed.
Step1. Create new Design for report under visual studio
Step2. Add code to method:
Add Code in the before TTSCOMMIT:
addOther(PrintMgmtDocumentType::SalesOrderPackingSlip, ‘SalesPackingSlip.Report_XYZ,’SalesPackingSlip.Report_XYZ’ ,’XYZ’);
Step 3. Setup the Format under:
AR -> setup -> form setup -> Print management -> Sales order Packing slip
original -> report format to SalesPackingslip.Report_XYZ
New Report design can be executed from use Print management from Inquiry journal forms or during posting by selecting Print management destination.
More Links for Reference:
In the class and method CustAgingReportDP\processReport on line 85 there is this line:
The line above calls out to the CustBalanceList class which inherits from CustVendBalanceList. In method calculateDetailsForMultiple in CustBalanceList on line 5 there is this line:
custVendAgingCalculateTmp = agingCalculation.process(_queryRun);
That lines calls out to the process method in the CustVendAgingCalculation class. The process method is a driver method in which the data is collected that is later displayed in the report. The process method is a good place to set your breakpoints. On line 14 of the CustVendAgingCalculation\process method it collects all of the customers (or vendors) the report is going to look at. This is the line of interest:
On line 20 of CustVendAgingCalculation\process it grabs the open and closed transactions that will be displayed in the report. If you look at the CustVendAgingCalculation\selectTransactions method you will see it has two separate calls:
Both the selectClosedTransactions and selectOpenTransactions methods query the CustVendTrans and CustVendTransOpen tables for data. The methods insert what they find into a CustVendAgingProcessingTmp table. The details for the transactions are collected in the CustVendAgingProcessingDetailsTmp table and then both the CustVendAgingProcessingTmp and CustVendAgingProcessingDetailsTmp tables are combined into a single CustVendAgingCalculatedTmp temp table in the CustVendAgingCalculation\process method. Once everything has been pulled together, the CustVendAgingCalculatedTmp table is returned to the CustBalanceList\calculateDetailsForMultiple method.
Next in the CustBalanceList\calculateDetailsForMultiple method the insertIntoTmpAccountSum method is called. In the insertIntoTmpAccountSum method the contents of the CustVendAgingCalculatedTmp table are inserted into a CustTmpAccountSum temp table. At the very end of the CustBalanceList\insertIntoTmpAccountSum method the TmpAccountSum is an instance of the AccountSumMap. The map is set equal to the CustTmpAccountSum table. The mappings on the AccountSumMap map translate the fields in the CustTmpAccountSum table to an instance of the TmpAccountSum temp table.
The TmpAccountSum table is then used by the CustAgingReportDP\processReport method on line 90 with this call:
The contents of the TmpAccountSum are inserted into a CustAgingReportTmp table and this temp table is what is returned to the SSRS report design.