-
Product/Item/Resource name field to Inventory Value Report Storage
The new Inventory Value Report Storage contains many useful fields in order to visualize inventory values but Resources are displayed only by the ID. Now the customer is not able to verify what the resource represent. So adding the resource name field to the report or parameter into Inventory value reports inventory dimensions table could make the report even better. -
Allow edit positive depreciation parameter in the middle of fixed asset service life
A fixed asset has a positive acquisition value in the beginning of service life and it's depreciated with some negative amounts. During the service life of this fixed asset, there is a donation or the fixed asset will be sold that (adjustment) puts the net book value to a negative amount. After that positive depreciation's should be able to post automatically, when Parameter "Allow positive depreciation" is activated. Now the parameter is locked after very first deprecation so new design is needed in order to take account this kind of business event.
-
New created by field to D365 forms that show the user id who have created the record
There is possibility in many forms to add field called created by to list view so that user can check who have actually created the record. For example in All customers form you can add created by field based on tables Global address book, People, Worker and Person name. Created by field from Global address book (DirPartyTable) shows in most of the cases the correct user id who have for example created the new customer but not always. That's why new created by field is needed at least for All customers and All vendors forms. New created by field should fetch correct user id from table location that shows the user id who have created the new record. In All customers form the correct id could be retrieved from CustTable and in All vendors form VendTable shows correct user id in created by field.
-
Tax direction validation on vendor invoice approval journal should be fixed
When trying to post cost invoice in invoice approval journal where are two project type of lines (credit and debit) and two different sales tax codes used (VAT25,5 and VAT0). Only the amount of VAT will be paid for the vendor. Posting will end up in error: Tax direction must be specified on ledger account . No specific ledger account is mentioned in the warning. VS debugger shows that validation try to find sales tax direction for "empty" ledger account. Posting will passthrough when GL Sales Tax parameter Tax direction requirement is switched off. All needed ledger accounts have tax direction. SingUp Software's ExFlow AP automation is used. Posting of approval journal is standard functionality. Tax direction validation in this case was working in version 10.0.36 but not anymore.
You’re offline. This is a read only version of the page.
