Comments
Hello,We have 20 Affiliates in Europe and Africa,And we're trying to automatize as much as possible deployments and environments configuration as we used to do with Navision and Powershell modules Microsoft.Dynamics.Nav.Management.dll Microsoft.Dynamics.Nav.Model.Tools.psd1,But it seems not all "Functionalities" are accessible with APIs.In my opinion, options available in UI should be too in APIs.Best regards,J-F
Revision for point number 3. A reconciliation rule with Action 'Mark new transactions' also provides an option for default Account type, Ledger, and Financial dimension option, so that once a rule runs for Mark new transaction, the new lines have Ledger, dimensions, and description by default. Reason: A transaction code in the bank statement can have multiple kinds of transactions from a business perspective. For example, bank statement transaction code number 699 shows various payments like Vendor payment, GST payment, Income tax payment, Payroll payment, withholding tax payment, etc with references. Businesses can create multiple rules based on statements for transaction code 699 which can auto-create new transactions but as 'Transaction code mapping' only supports one statement code to one D365 bank transaction type, it is not possible to assign different accounts. It leads to manual work and increases business costs. It would be good If the Main account type, account, description, and financial dimension could be available on Mark new transaction page. Once the rule runs, it should update the New transaction line with Account and dimension, description.