Hi Microsoft Dynamics AX Community, I would like to inform you that AXPulse R&D team is working on one of the Microsoft Dynamics AX 2012 add-on for the services industry. With this add-on, you are now able to update the existing and open project cost commitments with the updated item pricing through trade agreements. Let’s consider this scenario – you have number of active projects with open orders. Those open orders have also created committed cost entries in the project module. Let’s suppose your organization have updated the item pricing and now want to update all the open committed cost entries. With this AXPulse add-on you will be able to update the existing open committed cost entries with the updated item pricing.
AXPulse will be releasing this product. Stay tuned. Happy weekend.
Hi everyone, we are back again with a new feature in the Power BI Desktop that we will cover in this blog post is Power BI Templates. This feature allows users to export a Power BI Desktop report as a template (PBIT file), which can be instantiated as a new Power BI Desktop report (PBIX file).
A Power BI Report Template contains the definition of the Report, Data Model definition and Queries definition. In other words, a Power BI Report template includes pretty much everything that a Report file includes, with the exception of the data itself.
Today we will walk you through developing a Power BI Template with query parameter, another exciting feature that gives good combination with Power BI template which you will get to know as we will move on.
First we will design a report using map visual in Power BI and AX 2012 ODATA Query Service as its data source.
To design map visual in Power BI, you can refer to one of my blog via: http://www.axpulse.com/tag/google-maps/
Now we will make a query parameter in our Power BI map visual report. As query parameters allow users to easily make parts of their reports and data models (such as a query filter, a data source reference, a measure definition, etc.) depend on one or more parameter values.
In Query Editor window, Click on Manage Parameters -> New Parameter and input the following information as shown below:
I had provided Current Value field with my ODATA Query Service URL and ProjectRegionwise at the end of URL is my custom query name in AX 2012. The Current Value field is optional you can also leave it as blank.
As soon as you click on OK, you will see that in Queries pane another query get appear with the name you provided to the parameter.
In our case its AX 2012 ODATA URL, now select ProjectRegionwise query and set its formula to = OData.Feed(#”AX 2012 ODATA URL”) as shown below:
Now Refresh the Preview and then Close & Apply changes. We are just one step away to build a template and you will see the automation that will be provided by our query parameter.
Click on File -> Export -> Power BI Template and fill in the Description as shown below:
Press OK and specify the location to save the template file. The template will get save with extension .PBIT, Notice that the size of Power BI template is always less than its original Power BI report .PBIX file as you can see in the screenshot:
Open the recently created template file by double clicking on it or import it through Power BI Desktop. You will see a dialog prompting you to input your ODATA Query Service URL that is the query parameter we had created while developing the Power BI Template.
After providing the dialog with your AX 2012 ODATA Query Service URL, a new Power BI Desktop report based upon the contents in the template file would be created exposing your own data in map visual.
That’s all about Power BI Template. I hope you get better understanding of building Query Parameter with Power BI Template because together these rock the Power BI plateform.
Microsoft has planned to release the cumulative update 13 of Microsoft Dynamics 2012 R3 during Q3 of 2017.
AXPulse team was recently involved in yet another upgrade project. The customer was a manufacturing giant, had around 12 legal entities, 600 gigs of data, 150 application users, multiple AOS, data was heavily virtualized and guess what? They were on Microsoft Dynamics AX4.0…and wanted to upgrade to Microsoft Dynamics AX 2012 R3.
During the upgrade, we encountered a number of scenarios where we had to write custom scripts for data upgrade and cleansing, made use of State Transfer Tool to mitigate the risk of Production system cut off time available and multiple sessions with the customer users to run the upgraded application for testing. Dedicated time was spent on multiple passes before the actual Production upgrade just to make sure that our approach towards the GoLive is aligned with customer business operations. AXPulse team worked on multiple weekends to simulate the cut off and GoLive preparation and finally it paid off.
Overall a very exciting journey with the customer to achieve a successful GoLive with great learning for the team that boosted our confidence for more such upgrades.
More stories to come…
Proficient consultants and developers at AXPulse have yet again progressed in their continuous quest of upgrading AX functionality by introducing an add-on of advance payroll tax engine to Payroll module. With the help of this add-on, Payroll Department can create and manage tax deductions to the monthly pay statement as prescribed by the tax authorities of the applicable jurisdiction.
Terminologies used in this article:
TAX COMPONENTS: This is where the different constituents which contribute to tax payable in a period are defined such as gross salary and taxable income.
TAX CATEGORIES: This allows to define the different taxable sources in an organization such as local and overseas employees, or the payroll tax payable by employer in certain jurisdictions.
TAX CATEGORIES GROUPS: Different tax categories can be grouped together which represent different applicable tax rates.
TAX RULES: Perhaps the second most important part of configuring periodic payroll tax, this is where the source/nature of rules that define if the employee’s income is tax deductible or exempt are defined. In simple terms the tax bands of the jurisdiction are defined here.
TAX RULE GROUPS: Different criteria defined as tax rules can be grouped here.
TAX CALCULATION CODES: This is the calculation hub and the most important feature of this add-on. Different calculation codes/formulas can be assigned to the tax components based on the pre-defined tax rules.
- Install Advance Payroll Tax XPO
- Disconnect the current/standard tax functionality and the default tax region applicable on each employee.
- Assign Tax Category to each individual worker. Setting up tax categories is further defined later in the blog.
- Define the fiscal period in the Effective to and from field in order for the functionality to calculate taxable salary on annual basis.
This allows to define the different taxable sources in an organization such as local/overseas employees or the employer. Tax Category is assigned to each worker for tax purposes.
Workers are assigned to the tax category on individual basis.
Each tax category can be assigned a separate calculation code.
This is where the different constituents which contribute to tax payable in a period are defined. These tax components will later be used in tax calculation codes.
This is perhaps the second most important part of configuring payroll tax add-on. The source/nature of rules that define if the employee’s income is taxable or exempt is defined in this form. The tax rules also define the exact tax band in which the taxable income of an employee falls.
Similar rules can be grouped together in order to filter the rules on formula form based on rule group selected. For example salary based or employees country of origin/last permanent address/country of residence etc.
This is the calculation hub and the most important feature of this add-on. Different calculation codes/formulas can be assigned to the tax components based on the applicable tax rules.
The fixed amount and the variable percentage applicable to each tax band is defined here.
Furthermore the annual taxable income is calculated on annual basis by considering the remaining future months available if there is an increment in the monthly salary payable to the employee. Monthly tax liability is calculated with the help of tax liability payable in the future remaining months adjusted with the tax liability settled in the past months of the fiscal year.
Each calculation code can be assigned to many tax categories.
Finally generate earning statements and view a pay statement to observe tax deduction line in accordance to the tax bands defined in tax rules and the annual fixed amount and variable percentage defined in calculation codes.