-
Have an ability to create a Workflow condition on the PO header for the Dimension values entered in the Accounting Distribution form for the line details
Our customer would like to create a workflow that checks for specific department values for their Vendor Invoices. They are entering the account distributions by going to Financials | Distribute amounts for each of the lines in the Pending vendor invoice form (Accounts Payable | Invoices | Pending Vendor Invoices) The customer would like to setup a Vendor Invoice workflow that has a condition for a specific department value that was entered in the Distribute Amounts form. They do not want to create a Vendor Invoice line workflow and they would like all the verifications done via the Vendor Invoice workflow (header). We have already tested using the following Department fields: Purchase order lines.LedgerDimensionDepartment Accounting Dimension.Ledger dimension.department All the default Department fields This functionality is currently not available in D365 and our customers would like to request to have this feature as this is needed for their Business processing
-
Have an ability to create a Workflow condition on the PO header for the Dimension values entered in the Accounting Distribution form for the line details
Our customer would like to create a workflow that checks for specific department values for their Vendor Invoices. They are entering the account distributions by going to Financials | Distribute amounts for each of the lines in the Pending vendor invoice form (Accounts Payable | Invoices | Pending Vendor Invoices) The customer would like to setup a Vendor Invoice workflow that has a condition for a specific department value that was entered in the Distribute Amounts form. They do not want to create a Vendor Invoice line workflow and they would like all the verifications done via the Vendor Invoice workflow (header). We have already tested using the following Department fields: Purchase order lines.LedgerDimensionDepartment Accounting Dimension.Ledger dimension.department All the default Department fields This functionality is currently not available in D365 and our customers would like to request to have this feature as this is needed for their Business processing -
Have the ability to setup a workflow condition using the dimension values setup in the Accounting Distribution form for the Pending Vendor Invoice transactions
Our customer would like to create a workflow that checks for specific department values for their Vendor Invoices. They are entering the account distributions by going to Financials | Distribute amounts for each of the lines in the Pending vendor invoice form (Accounts Payable | Invoices | Pending Vendor Invoices) The customer would like to setup a Vendor Invoice workflow that has a condition for a specific department value that was entered in the Distribute Amounts form. They do not want to create a Vendor Invoice line workflow and they would like all the verifications done via the Vendor Invoice workflow (header). We have already tested using the following Department fields: Purchase order lines.LedgerDimensionDepartment Accounting Dimension.Ledger dimension.department All the default Department fields This functionality is currently not available in D365 and our customers would like to request to have this feature as this is needed for their Business processing -
Have the ability to select the default dimension for Payroll allocation
In D365 8 and via Hotfix kb 413260 for D365 7.3, there was a change made to the code to fix an issue with the Hour Transaction journal posting. On previous builds, the payroll allocation dimension was pulled from the Worker dimension. This was changed with the hotfix and in D365 8 so that Hour journal transactions post consistently using the Project default dimensions for the payroll allocation lines and work the same way as the timesheet entries. The ask is to have a parameter setup that allows for users to define where they would like to default the payroll allocation dimensions from.
-
Report Wizard in Dynamics 365 For finance and operations
Bring the Report Wizard back. The report wizard guides less experienced users through the design process. Advanced users can create new report building blocks or modify existing building blocks to meet their requirements. This feature used to be in Management Reporter 2012 but has been deprecated in D365 for F&O. We would like to request for this feature to be brought back as this was a really handy wizard to have for new users.
-
Allow Memo fields like performance review Description to be added via the Personalisation form
Memo fields cannot be added to the grid through personalization Repro steps: Navigate to the Reviews form. Click on the link to a review to open the details form. Navigate to the Activities tab. Right-click on the grid header and select Add columns. Results: The Description field is not included in the list of fields to add. Users would like to view the Description field in the Activities form to make it easier for users to view the information
-
Ability to view the receipts attached to each of the lines when in Grid view in the Expense Report
1. Create an Expense report. 2. Create 2 Expense line within the Expense report and attach a receipt for each Expense line. 3. Change view to Grid view. 4. In the Grid view, User will be able to see that the Receipts has been attached on each line, but there is no standard functionality that allow user to see the attachment for each expense line on the Grid view. The request is to have the ability to drill back to the receipts for each line when in Grid view. -
Make MTD (Making Tax Digital UK) feature available in all legal entities
Description of problem: Making Tax Digital functionality (ER configurations, data packages etc.) works fine only for entities with country\region = GBR. It has been assumed that company needs to be located in UK to be a UK tax payer. This assumption is completely incorrect. A company from any country/region in the world can be registered as UK tax payer (therefore, it will be mandatory for such company to provide VAT return declaration through MTD). Such company is called as non-established taxable person in UK. We have a customer with many entities - one of them is UK entity - located in UK and paying taxes in UK - we can setup MTD for this entity without any problem. Another of entities is New Zealand entity which, in the same time, is non-established taxable person in UK. Therefore, this entity needs to pay taxes in NZ (and it's located in NZ so country/region must be set to NZ) and the same time pay taxes in UK (through MTD). We tried to change validation in ER elements but even after adjusting validation to allow NZ country/region to use it we still have errors from Electronic Messages framework that this functionality does not support the country/region of the current entity (which like I explained is a mistake). It is not possible to split this into two entities because of many legal reasons. This suggestion is to allow for the MTD feature to be available for legal entities that are not setup as UK entities to but are paying UK taxes to be able to use the MTD feature. -
Mass Update module access in the Ledger Calendar form
In AX 2012 and above, there is a feature in the Ledger Calendar form that allows users to Update Module access. There is a request to be able to select multiple modules in one go and do a Mass Update module access. The current design only allows for one module to be selected at a time. It will save time if the system allows for multiple modules to be selected in one go similar to when doing a mass change of period status.
-
Have the option to assign the same Invoice number from the Project Invoice Proposal Number to the Project Invoice after posting
The customer would like the ability to match the Project Invoice proposal number with the Project Invoice number during the posting process. The system is currently defaulting the Invoice number from the next number sequence for the Invoice Number sequence. The customer has a business need to match all their invoice numbers so that the Invoice proposal and the posted invoice has the same number.