After a couple hours of troubleshooting, discovered the cause was the Depreciation profile Calendar setting set to Fiscal/Period instead of Calendar/Month. Setting to Calendar/Month resolved the issue.
For users of Dynamics AX and Dynamics 365 for Finance & Operations
Tuesday, June 23, 2020
Fixed Asset Depreciation Proposal Producing Inconsistent Results
D365 F&O, PU 34. Fixed asset depreciation proposal was working inconsistently across assets in the same company, and across companies as well. Some assets in one company were depreciating, while others weren't. Likewise, assets were depreciating normally in some companies and not others.
Tuesday, September 17, 2019
Processing a Customer Refund directly from Customer Payments Journal
I just learned this in the past week. Did you know you can issue a Customer Refund without creating a Vendor and an AP Voucher? It's true - you can process a payment to a Customer in the Customer Payment journal, exactly the same way as processing a Vendor payment in the Vendor payment journal. Thanks to my friend Kingsley Abu for opening my eyes.
Check (pun intended) it out!
Wednesday, January 16, 2019
How to Change the 'Person' Associated with a User
Needed to change the Person associated with a User and discovered that if you select Maintain versions in the Users menu bar, you can edit the Expiration date on the record.
Set the date to a day previous to today's date, Save.
The Person field is cleared and you can select a different value.
Set the date to a day previous to today's date, Save.
The Person field is cleared and you can select a different value.
Friday, January 4, 2019
New Dual Currency in F&O v8.1 - Fixed Asset Considerations
The new Dual Currency features added in version 8.1 include elements beyond just the General ledger. A number of modules are impacted, including Fixed assets. (Read about Dual Currency here).
Reading through the above article addresses the changes in Fixed assets. However it does so more from an upgrade perspective rather than a new implementation. During regression testing for a new implementation, we discovered that the Wizard referenced in the document MUST be run even though there are no transactions in a new database, and it must be run on every company that will have Fixed assets in it. Failure to run the Wizard will prevent running an Acquisition or Depreciation Proposal. The following error message is thrown if the Wizard is not run.
When running the Add reporting currency amounts to fixed asset books Wizard, you must run it through to the end of the process, even if no transactions appear in this form.
Then, you must select Yes in this form before clicking the Finish button.
This process executes in batch mode by default, so allow some time for the Wizard to complete processing before entering any asset transactions.
Note: A similar Wizard exists for Cash & Bank transactions as well. Make sure the Wizard process is completed before entering Bank transactions.
Wednesday, January 2, 2019
D365 F&O 8.1 Release Notes
For those who may not have seen them yet, here are the D365 F&O feature enhancements being rolled out between October 2018 and March 2019. There are some really cool features like real Dual Currency and Derived Financial Dimensions that add much-desired functionality to the app. Click on the image below and enjoy!
D365 F&O Keyboard Shortcuts List
Just discovered this today. You can open a list of shortcuts from anywhere in the application. Right click>>View shortcuts opens this form.
Sunday, August 13, 2017
D365 for Ops System Email Template Setup - HTML vs. XSLT
We were getting an error in a workflow (Root element is missing) that leverages the System email template found in System administration>>Workflow>>Workflow parameters>>Email message. Note the references to HTML in the 'Upload email template' form below. This would lead one to believe that the template uploaded must be in HTML format.
However, what we found was that during setup of this email template, XSLT was defaulted into the Layout field below. The problem is, the Layout field is not exposed in this form by default. We had to personalize the form to add the field.
The cause of the error was the mismatch between the Layout type (XSLT) and the HTML template that had been uploaded. Once we discovered the mismatch and changed the Layout value to HTML, the email error was resolved.
Subscribe to:
Posts (Atom)










