As with new Dynamics AX there are some changes in the Setup for EU sales list we created a short description with screenshots.

EU Sales list for new Dynamics AX (A7) in Contoso demodata DEMF_Example Germany

Have you ever created your Aging Period Definitions, run the Customer aging snapshot, and do not receive any results in the Collections Grid? If so, this could be a result of the format used in the Aging Period Definition name.

I have recently discovered that commas in the Aging Period Definition name are treated by SQL as special characters, and cause conflicts when running the Customer aging snapshot. The good news is there is a simple fix to resolve this issue.

Aging Period Definitions are setup under Accounts Receivable > Setup > Collections > Aging period definitions.

Example with commas which produce no results in the Collections grid after running Aging.

Example with underscores which produce results in the Collections grid after running Aging.

If you do not use numbers in the Aging Period Definition and use alpha characters, be sure that no commas exist. The same results will be encountered with alpha characters and commas.

Once you have made the changes to the Aging Period Definition be sure to remove the incorrect one. When running the Customer aging snapshot re-select the Aging period definition. The Customer aging snapshot is run by going to Accounts receivable > Periodic > Collections > Customer aging snapshot.

Access to Lifecycle Services site: https://lcs.dynamics.com

Select a project in your list (if you need to create a new one, click + and fill in the mandatory information requested).

Click on the Issue search application:

In the issue search page, click the Find icon:

In the filter, select different parameters to be able to find the relevant information:

For localization e.g. for Italy:

Add Open and Resolved in the Status area for AX products.

Then the result can be sorted by Date descending to have the latest released hotfix displayed first:

With a green bar, the resolved topics are listed, with a red bar the topics in process are listed.

Title, version, type, KB and released date are the information available for Resolved topics.

Title, version, type, status or planned date are the information available for Open topics.

This is to inform you that we have released a country-specific update for Denmark and Austria to support attachments in electronic invoices in Microsoft Dynamics AX 2012 R3.

Overview

This update allows to support attachments inclusion into electronic invoices output XML files according to UBL requirements.
After the installation of this hotfix, the following XSL transformation files need to be extracted from the package and uploaded to replace the existing transformation files:

• Denmark: “eSalesInvoice_DK_OIOUBL.xsl” and “eProjectInvoice_DK_OIOUBL.xsl”;
• Austria: “eSalesInvoice_AT_OIOUBL.xsl” and “eProjectInvoice_AT_OIOUBL.xsl”.

Download information

KB3151026 | LCS

Microsoft Dynamics AX Bank statement import setup for MT940

Please find in the attached document short instructions for setting up Bank statement import based on format MT940.

The instructions applies to Microsoft Dynamics AX (AX7).

When you deploy a cloud-hosted Dynamics AX 2012 demo environment from Lifecycle Services (LCS), the password for Administrator is fixed and well known.

We have discovered that this causes unauthorized usage via RDP and hackers can use it to spread viruses and malware.

After the AX 2012 demo environment has been deployed to Azure, then you should change the password for the Administrator account.

In case you should forget the administrator password, it can be reset https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-windows-reset-rdp/

Note that there are a few other user accounts that also have administrator permissions which could be used for remote access. Since some of these user accounts are used as service account there will be quite a job to change password on these accounts. Therefor an option is to restrict the allowed IP addresses in the firewall. Here are some articles about that:

https://technet.microsoft.com/en-us/library/cc753558.aspx

http://www.cm3solutions.com/block-ip-address-ip-range-using-windows-firewall/

http://superuser.com/questions/268902/how-to-block-all-traffic-but-one-ip-in-windows-firewall

There can be situations where you need to cancel an exchange adjustment. This could be because the wrong exch.rate was applied or because you in hindsight find out it would lead to reconciliation issues if you did not do the reevaluation from the ‘right’ module.

Here I will show an example of how to cancel an exchange adjustment when you by accident did in General Ledger, but actually needed to do it from Accounts Receivable

These are my exchange rates

I post a freetext invoice on Feb 1^st in USD

My Summary account balance in my company currency is 19444.44

I decide now that I want to do an exchange adjustment for my summary account 130100 to update the balance with the rate of March 1^st

After the exchange adjustment, my trial balance looks like this

My summary account balance after the reevaluation is 19662.92

However, now I find out that I should actually have made an exchange adjustment from Accounts Receivable(AR) instead.

The problem now is how can I cancel this exchange adjustment so that I can do it from AR instead

The easiest way to do that is to change the exchange rate on March 1^st to be equivalent to the one from Feb 1^st

90 for March 1st

We can then rerun the exchange adjustment and note that my Trial balance shows that the balance on my summary account is back to 19444.44.

The previous exchange adjustment has been cancelled out and I can update my exchange back to 89 and do the exchange adjustment from Accounts Receivable

This content is password protected. To view it please enter your password below:

Password:

Scenario:

A custom cue has been created and you want to add this cue in addition to some standard cues to a specific role center so that all users of the role center can see the cues.

When user A (e.g. an Administrator) adds the Cues web part to a role center page and add cues to the web part, user B logging in to the same role center can see the web part but can’t see the cues.

When user B try to add the custom cue to the Cues web part, then the custom cue is not found in the cues list.

So why does this happen?

If you add cues one by one to the Cues web part then the cues will be saved per user in the AX tables (SysCueGroup, SysCuePersonalization, SysCueGroupMembership), so only the user who added the cues can see the cues.

The cues are based on queries/tables so it will be the permission granted for the queries/tables in AX that decides if you can see the cues or not. So what cues a user has access to will be based on the assigned roles and what permission these roles have for the query/tables the cue is based on. This means that the roles assigned to user B does not have permission to view the custom cue and the data in it. The user can only see/add cues he/she have permissions for.

How you can achieve the goal described in the scenario above:

Add your cue to a Cue Group in AOT > Parts > Cue Groups.

Add a Cue webpart to a web page in shared mode (Site Actions > Edit Page) and click on Edit webpart (arrow in upper right corner of the webpart). In edit webpart specify a Cue Group Name and click Ok to save and close.

When other users log in to the same role center, they will see the cues they have permissions to in that group.

You can use the standard cue groups and if the users of a role center need to see cues from several groups then you need to add one Cue webpart for each cue group.

Or you can create your own cue groups, e.g. one group for each role center and in each of the cue groups add the needed cues and then use these groups in the cue webpart.

Edit web part:

Result on role center:

Some additional information:

The difference between editing the shared and personal web page is:

If you use Site Actions > Edit Page – then you edit the shared web page.

If you use “Account menu” > Personalize this Page – then you edit the personal page.

Some documentation about cues in AX 2012 on MSDN/TechNet:

Cues and Cue Groups

Manage cues (Enterprise Portal)

Manage Cues on Role Center pages

Set up user security in Microsoft Dynamics AX 2012

There can be times when you are unsure of how and why a certain feature works in AX. For example how a certain field is calculated or the effect of defining a particular parameter. For this, it is often useful to go ‘under the hood’ to get a direct view of the logic in place.

In this blog we will see how we can use the AX cross reference system to help us locate the exact places in the code where the feature you are interested in has been coded in. For more on the AX crossreference system and in particular how to set it up, you can consult this site https://msdn.microsoft.com/en-us/library/aa877386.aspx

Example

In this example I am interested in learning how and where the AX error account is used in the system. To find out, I would do the following steps

1. Locate the form where the feature I am interested in is defined. In this case, General Ledger\Setup\Posting\Accounts for automatic transactions

2. Once I have opened my form, I want to know more about the settings of the ‘Error account’

3. The first thing I would do is find out the name of the table and field that is listed in the form here. To do this, the easiest way is to rightlick and select ‘Personalize’

4. Note then how the focus on the left pane is on the field you put your cursor in, in this case ‘Posting type’ and to the right, you can see the table name and associated field

In this case I can see that the posting type field is associated with the table ‘LedgerSystemAccounts’ and the field is ‘Code’

5. I go to the AOT, short cut from the application is pressing Ctrl + D and locate the ‘LedgerSystemAccounts’ table(DataDictionary\Tables) and go to the field ‘Code’

On the ‘Code’ field I rightclick and select ‘Properties’ and take a note of the Enum type of the field as I know the field is an Enum(a drop down list). I note the enum is called ‘LedgerPostingType’

6. I proceed to locate this enum by going to Data Dictionary\Base Enums

I expand the ‘LedgerPostingType’ enum and go to ‘ErrorAccount’ as this is what I am interested in

On the ‘ErrorAccount’ node I righclick and select ‘Add-ins\Cross-reference\Used by

And the cross references form appears

And I can now see the places in the code where it is defined when the system will post to the error account

There are many ways to raise a new service incident to Microsoft Dynamics AX support team: PartnerSource, phone call and others. With Lifecycle services portal Microsoft has introduced a new possibility for partners/customers – Cloud-powered support. Cloud-powered support is a part of Lifecycle Services that helps you manage support incidents. And comparing other channels – Cloud-powered support offers to partner create a virtual machine (VM) attached to incident.

The process of submitting a new incident is different for each partner/customer according to support plan they have.

• Partners with No Service Plan
  
• Partners with Service Plan
  
• Premier customers
  

Partners with No Service Plan

1. Create a new incident trough PartnerSource
   
   1. Log into PartnerSource, and select your customer.

    

   1. On New Support Incident page select “Microsoft Dynamics AX Business Value (2012)” , other product versions with (Powered by LCS) note would take you to LCS

    

   1. Fill in all required data and submit the incident.

    

2. Link new service incident to customer project in Lifecycle Services
   
   1. Open Lifecycle Services, and without entering any project go to Manage incidents section

    

   1. On Manage incidents page select customer account you have used in the step 1, and locate the service incident. Select it and click “Link to Project”
   1. Select customer LCS project for linking and click Save

       

   2. Service incident is correctly associated to project now.
   1. And is visible also from Cloud-powered support section of the project:

3. Add Virtual Machine to Service request
   
   1. On Manage incidents / Project incidents page click “Add VM”

    

   1. Decide whether you want to use template for virtual machine (faster and recommended method) or you want to use System Diagnostics, and LCS will prepare the VM based on version from customer environment (slower):

1. On Manage incidents / Project incidents page click ‘View’ case details to check VM status and see connection details:

1. Notification email is sent to Project owners, and user who requested the VM once the VM is ready.

Note: Partners with no service plan will receive an error message “CPS does not support pay-per-incident support plans. Please contact Microsoft support directly.”

Partners with Service Plan

1. Open customer LCS project
   

    

2. Go to Cloud-powered support section
   

3. Create a new incident
   
   1. Click ‘New Incident‘ at the bottom of the screen
   2. Use Issue search for existing solutions
   1. Click ‘Create incident’ in case you haven’t found any solution
   2. Select environment from diagnostic data (available only if System diagnostics was installed on customer machine)
   1. Describe the issue, and answer severity questions
   2. Decide whether you want to create VM for the service request or not, and whether template for VM should be used (faster and recommended method) or you want to use System Diagnostics, and LCS will prepare the VM based on version from customer environment (slower):
   1. Submit the incident

       

   2. On Manage incidents / Project incidents page click ‘View’ case details to check VM status and see connection details:

    

   1. Notification email is sent to Project owners, and user who requested the VM once the VM is ready.

Premier customers

1. Open LCS project
   

    

2. Go to Cloud-powered support section
   

1. Create a new incident
   
   1. Click Premier tab
   2. Click ‘New Premier incident’
   1. Use Issue search for existing solutions
   1. Click ‘Create incident’ in case you haven’t found any solution
   2. Select Premier contract from the list or add a new Premier contract; click Continue
   1. Select severity of your issue. Note: severity AX cases cannot be created through LCS, it is necessary to call Microsoft Premier support.
   1. Enter issue details – topic, title, description; you can also upload 3 files.
   1. Enter contact details
   1. Review all data and click Submit to process request to support team

2. Add Virtual Machine to support incident - follow instructions in section “Partners with No Service Plan”, point 3
   

   
    

I recently had the following error show up in my queue.

An unexpected exception occurred during setup. See the log file C:\ProgramData\Microsoft\Dynamics AX\Dynamics AX Setup Logs\2016-02-03 22-34-07\DynamicsSetupLog.txt for details.

I myself had encountered this (or similar) error when installing some hotfixes. At the time I would review the log and determined whatever had caused it hadn’t affected the installation of the hotfix so I continued working, thinking it was likely a minor issue with our internal test VM.

When I saw that a customer had reported the issue it provided an opportunity to look into it further in case there was an larger issue. Unfortunately, there wasn’t much I could look into so I confirmed that I could reproduced the above error and submitted it to our InMarket Development team to investigate.

They were able to determine that it was an issue stemming from WPF and not something specific to installing the Dynamics AX hotfix. In their testing, restarting the installer or the machine, the same installer wouldn’t throw the error. Unfortunately, this also meant that we didn’t currently have a fix for the issue other than to provide some education on what was causing the issue.

Hence this blog.

So if you encounter the above error when installing an update to Dynamics AX, you have the following options.

• Verify the model is installed (for an application fix) or the build number matches (for a kernel fix) – Recommended
• Rollback/restore the database prior to install, run the installer again
• Rollback/restore the database prior to install, restart the machine, run the installer again

Hope this helps!

Attached you will find a description on how to use notes on header and lines when using eInvoice for Norway.

How to use notes on header and lines when using eInvoice for Norway

To use currency translation in Management Reporter, you must first set up your currencies and rates in AX. The following lists the items that must be set up in AX.

• Currencies (General Ledger | Setup) – currencies are created
• Exchange Rate Types (General Ledger | Setup) – exchange rate types are created (aka Exchange Rate Tables)
• Currency Exchange Rates (General Ledger | Setup) – where exchange rates are entered for the exchange rate types
• Ledger (General Ledger | Setup) – the following translation related settings found here
  • Accounting Currency (Functional Currency)
  • Reporting Currency (Secondary Currency)
  • Default Exchange Rate Type
  • Default Budget Exchange Rate Type – Budget data can be translated using a different rate by specifying a different exchange rate type.

• Main Accounts (General Ledger | Common) – translation settings specified on the account
  • Exchange Rate Type – Specifies which exchange rate type the account will use.
  • Currency Translation Type – specifies which translation type the account will use. You can select either Current, Average, Weighted Average or Transaction Date.
    • Current
      • Typically Balance Sheet accounts
      • Uses period end (report date) rate
    • Average
      • Typically P&L accounts
      • Uses average rate for the period; (sum of rates)/(number of rates)
    • Weighted Average
      • Typically P&L accounts
      • Uses weighted average rate for the period; (rate*days in effect)/(number of days in period)
    • Transaction Date (Historical)
      • Typically Retained Earnings, Equity accounts and longer term fixed assets (i.e. Land)
      • Uses rate in effect on the date the transaction was entered

MR Setup

• No setup required but there are some settings that will change how translated amounts are viewed on reports.
  • Column Definition
    • Use the Currency Display if you want to restrict the column to only display data in the currency specified
    • Leave blank if you want to be able to view the data in other currencies. This can only be done in the Web Viewer.

  • Report Definition – “Include all reporting currencies”
    • Determines when reports are generated for the other currencies
  • Web Viewer Currency button – to view the report in a different currency click Currency and then select a different currency
    • Depending on the option “include all reporting currencies” the report will open or will need to generate before opening.
    • If any column had a currency specified in the Currency Display field that column cannot display data in other currencies.
    • When a report is viewed in a different currency, that currency will show in the upper left corner to easily determine which currency is being viewed.

Other notes\comments

• Consolidated reports with companies in the tree that have different accounting currencies will automatically do currency translation. The currency that the report is generated in is shown in the Report Definition
  • In the above example all companies will be displayed in USD. That currency defaults in from the company that is specified in the Report Definition. If @ANY is selected, the default currency will come from the company set as the default in MR Report Designer.

     

• As noted above, Retained Earnings (Accounts used in General Ledger | Fiscal Year Close | Opening Transactions | “Main account for transfer of year-end result:”) is typically set to use a translation type of Transaction Date. These accounts also have the following requirements to translate as expected in Management Reporter.
  • Must be assigned to the Retained Earnings main account category in the Main Accounts window like this to translate:

  • Account cannot have any transactions posted directly to it; only the system generated transactions created by the fiscal year close process.
  • There is one limitation with translation of the Retained Earnings account. Most users expect each year’s adjustment to RE to be translated at the rate that exists at the end of that given year. However the entire RE balance is translated at the rate that exists at the end of the most recent year closed. In other words, each year’s data is not translated at that year’s rate.

   

• In the Column Definition there is a field called Currency Filter. This is not related to currency translation. It can be used to filter a column to only show transactions entered in a specific currency. In AX if transactions were entered in two different currencies in the same company but data was needed for only transactions entered in one specific currency that currency could be entered as a Currency Filter. That column would then only show transactions entered in that currency.

   

• MR can return a translated amount even when there is a $0 balance in the Accounting Currency. A simple example to explain this:
  • An account is set to Transaction Date
  • Debit amount of 1,000 posted to the account on 1/15/2016. Exchange rate on that date of 1.1 so the translated amount is 1,100
  • Credit amount of 1,000 posted to the account on 1/22/2016. Exchange rate on that date of 1.2 so the translated amount is 1,200.
  • Report generated on 1/31/2016. The amount in the Accounting Currency is $0. The translated amount will be a credit of -100 (1,100 – 1,200).
  • This situation can occur with accounts set to Transaction Date or either of the Average translation types.

Rates entered in AX for USD to GBP that will be used by MR when doing currency translation.

YTD/BB Column

The report date is March 31^st. The columns are set to return YTD/BB data. The data comes from the year end process run on 12/31 so uses the rate from that date of .64418.

January Column

The report date is March 31^st. The columns are set to return January data. The rate used will be the rate in effect on 1/31 – .63428

February Column

The report date is March 31^st. The columns are set to return February data. The rate used will be the rate in effect on 2/29 – .62992

March Column

The report date is March 31^st. The columns are set to return March data. The rate used will be the rate in effect on 3/31 – .62451

YTD Column

The report date is March 31^st. The columns are set to return YTD data. The rate used will be the rate in effect on 3/31 – . 62451

Rates entered in AX for USD to GBP that will be used by MR when doing currency translation. The average rate is calculated by taking the sum of the rates and dividing by the number of rates in the period.

YTD/BB Column

Average translation type accounts are typically P&L accounts so they won’t have a beginning balance as noted in the screen shot showing no data. If a Balance Sheet account was set to Average each month’s balance that makes up the beginning balance would be translated at that month’s average rate.

January Column

The report date is March 31^st. The columns are set to return January data. The rate used is an average of all the rates that exist within January which calculates to .64292.

February Column

The report date is March 31^st. The columns are set to return February data. The rate used is an average of all the rates that exist within February which calculates to .63251.

March Column

The report date is March 31^st. The columns are set to return March data. The rate used is an average of all the rates that exist within March which calculates to .62873.

YTD Column

The report date is March 31^st. The columns are set to return YTD data. Each month’s balance is translated at that month’s average rate. The effective rate calculates to .63467.

Rates entered in AX for USD to GBP that will be used by MR when doing currency translation. The weighted average is calculated by taking the rates multiplied by the days in effect and divided by number of days in the period. (rate * days in effect)/day in period

YTD/BB Column

Average translation type accounts are typically P&L accounts so they won’t have a beginning balance as noted in the screen shot showing no data. If a Balance Sheet account was set to Average each month’s balance that makes up the beginning balance would be translated at that month’s average rate.

January Column

The report date is March 31^st. The columns are set to return January data. The rate used is a weighted average of all the rates that exist within January. Each rate is weighted by the number of days it is in effect which calculates to .64734.

February Column

The report date is March 31^st. The columns are set to return February data. The rate used is a weighted average of all the rates that exist within February. Each rate is weighted by the number of days it is in effect which calculates to .63259.

March Column

The report date is March 31^st. The columns are set to return March data. The rate used is a weighted average of all the rates that exist within March. Each rate is weighted by the number of days it is in effect which calculates to .63055.

YTD Column

The report date is March 31^st. The columns are set to return YTD data. Each month’s balance is translated at that month’s average rate. The effective rate calculates to .63677.

Rates entered in AX for USD to GBP that will be used by MR when doing currency translation.

YTD/BB Column

The report date is March 31^st. The columns are set to return YTD/BB data. The data is from a transaction that occurred during 2011. The rate in effect at the time the transaction was entered was .62820.

January Column

The report date is March 31^st. The columns are set to return January data. Below is a screen shot of the report followed by the transactions that exist within January. The effective rate calculates to .56286.

February Column

The report date is March 31^st. The columns are set to return February data. Below is a screen shot of the report followed by the transactions that exist within February. The effective rate calculates to .66524.

March Column

The report date is March 31^st. The columns are set to return March data. Below is a screen shot of the report followed by the transactions that exist within March. The effective rate calculates to .60211.

YTD Column

The report date is March 31^st. The columns are set to return YTD data. Below is a screen shot of the report followed by the transactions that exist within the year. The effective rate calculates to .63569.

In AX 2012, it is possibly to specify which user groups are allowed to post accounting transactions to a certain period for a given module by using the Ledger calendar form. The form is found in General Ledger>>Set up>>Ledger>>Ledger Calendar>>Module access level (please see screen shot below). Here, you can specify if All, None or specific user groups should be able to post to this period via the specified module. If there is a need to specify access for a group of users, the user group must be set up first. This is managed in System administration > Common > Users > User groups.

Below is a summary of the postings controlled by each module’s parameter in the above form:

Ledger

This parameter controls the posting of all journals in the modules General ledger, Accounts receivable, Accounts payable, Project and the posting of the periodic Exchange adjustment jobs in the modules General ledger, Accounts receivable and Accounts payable to the general ledger.

Customer

This parameter controls the ledger updates of Free Text Invoices and the exchange adjustment ledger postings caused by manual settlements via “Open transaction editing”.

Vendor (Supplier)

This parameter controls the exchange adjustment ledger postings caused by manual settlements via “Open transaction editing”.

Sales order

This parameter controls the ledger postings caused by sales order updates.

Purchasing

This parameter controls the ledger postings caused by purchase order updates.

Inventory

This parameter controls the inventory posting to general ledger via the journals Movement, Profit/Loss, Counting, and Inventory to fixed assets and also from the periodic job “Closing and adjustments”.

Production

This parameter controls all ledger updates from production journals.

Project

This parameter controls ledger updates posted by project invoice and on account invoice.

Payroll

Will be updated.

Sales tax

This parameter controls the posting of the periodic job “Sales tax payment” to the general ledger (when selecting “Update”).

Fixed assets

This parameter is currently without any function.

Bank

This parameter controls the posting to general ledger during bank account reconciliation when bank transactions are created.

Cost accounting

Will be updated.

Expense

This parameter controls ledger updates posted by expense reports.

How AX is intended to work using destination based tax for retail

How to set up Destination based tax for sales orders created in EPOS or MPOS?

Repro steps and setup (please refer to the document attached):

1. A Store should have a parameter ‘Use destination-based tax’ enabled.

2. Default Sales tax group is TX on a store.

3. Delivery address should be added and tax setup on a customer account:

On a customer account 2001, Tab Addresses you should add Delivery address (Cust-Ship) and then add Sales tax on Tab General (Sales tax TN):

4. Sales tax setup:

TX has 6,25 % tax

TN has 7% tax

5. In POS sell an item and select Shipping address:

In POS select an item 0113 with 99,99 price tax included, then enter customer 2001. Sales tax is taken by default from the store as TX and tax amount calculated 5,88.

Then click a button ‘Add shipping address’ and select created delivery address Cust-Ship.

Now Sales tax is taken TN from Shipping address and calculated 7% with amount 6,54.

———————————————-

In EPOS and MPOS Destination based tax works as described above, only if we have Sales tax group set on Customer Delivery address (it is explained on white paper).

Destination based tax set up on a Sales tax group is used only for ONLINE STORES.

Such information can be found on technet https://technet.microsoft.com/en-us/library/aa498345.aspx

When the user enters sales in web (online) store, selects a Shipping address, then the system is checking Destination based tax from Sales tax group.