Dynamics 365 Finance

Please provide a method in X++ that we can call to determine if the current environment is a production environment or not.

To Microsoft Team,

I am seeking your assistance in the development of a structured process for the creation of an API database import mechanism from Tier 1 Environment to Tier 2 Environment. The establishment of this database migration procedure is deemed imperative and promises to be advantageous not only for our customers but also for the testing engineers involved.

Your guidance and expertise in this matter would be greatly appreciated.

After posting a customer invoice, going into the document it’s not possible to add any free text and also field invoice description is not editable.

This is very strange as it could happens that for a claim you need to write something in it, when you send account statement to client this must be visible.

It is quite common request and all other systems (like SPA, Infor, Oracle) I see the editable text is there.

Then, a new text field on the header of invoice just to add some text is required.

Changing Number sequence of the Tags - Column Number in Financial Tags is not editable. 

It should be possible or rather it would be needed for the business to be able to change the Tag hierarchy and sequence. After Making an error when creating the Tags in Production environment it will be no possibility to fix it. 

As this feature is substitiution of having too many financial dimension, business should have possibility to update/change sequence of financial tags.

Today is out of scope the record 1601 for the generation of the fiscal SPED.

This record 1601 (OPERATIONS WITH ELECTRONIC PAYMENT INSTRUMENTS (VALID FROM 01/01/2022) depending on each federative unit, its generation may be mandatory from 2023.

See the page 301

Link:  http://sped.rfb.gov.br/estatico/83/641EFB2FC0E317FFF8A5A5D09E3C874F3CDB04/Guia%20Pr%c3%a1tico%20EFD%20-%20Vers%c3%a3o%203.1.3.pdf

New functionality Financial Tags to be Included in Financial Reports (MR). So we can group or see the details in the MR.

The Asset Leasing module is not able to account for partial months.  Not all leases start at the beginning or end of the month. As a result, business either has to modify the lease schedule to reflect what the module is capable of handling.

'Bulk editing in grids' is a feature On by default in 10.0.44. 

We request that this feature is never made mandatory as a user could inadvertently incorrectly mass update a grid, causing operational stop for the company and a major clean up issue. 

This feature should never be forced on clients and ideally Disabled by default, so clients have to directly opt-in.

The report "Service Declarations F01DGS" is currently unavailable in D365 Finance and Operations. However, it is essential for compliance with Belgian legal requirements. While this report is already available in Business Central, our customers have expressed a strong need for the report in D365 Finance and Operations to ensure seamless operations and adhere to local regulations.

When employee opens "Unattached expenses" function from "Employee self service" and adds some expense lines to her/his expense report than default dimension inheritance is not being executed.

Adding or removing Project ID to expense line does not have any impact on financial dimension values on this expense line (despite of correct rules/conditions being present in "default dimension inheritance" functionality).

As the result, expense lines processed with the use on "Employee self service" workspace have inaccurate financial dimension values in accounting distribution.

This problem does not occur if expense lines are processed in Expense Management module.

I suggest that execution rules for "default dimension inheritance" should be reviewed for Employee self service/Unattached expenses, so system inherits/recalculates financial dimension values whenever any change is made to Project ID on expense line. This would bring that functionality in line with how it works in Expense Management module and improve posting accuracy.

Described issue was experienced and persists in D365 Finance & Operation version 10.0.41 (10.0.2015.78).