on
RE:
This issue has a direct impact on the reliability of workflow validation in the purchase order process. Although all lines are properly distributed, the system returns an erroneous validation failure, preventing workflow submission.Our customer confirmed that the proposed workaround (disabling Auto Calculate Totals and Accounting Distribution) is not viable. It introduces a functional gap by bypassing critical distribution validation checks, which are essential to prevent downstream errors during invoice posting — such as missing financial dimensions.This behavior contradicts the intended integrity controls in D365FO and poses a significant risk to data quality and process control. The issue appears to be a regression or unresolved bug rather than a configuration gap and should therefore be prioritized for a permanent resolution in the standard product.We strongly urge Microsoft to reconsider and address this as a product defect, or at minimum provide an alternative workaround that preserves standard validation logic while allowing submission of POs that are in fact correctly distributed.
RE:
This could also allow you to process json payloads that don't fit within the structure of a page, so all for it!This seems to happen more and more often that we come across a json structure we cannot fit in the "rigid" structure of a page
RE:
This change would be especially useful when considering the standard Error Message table, which has a Context Record ID field.Consider the following use-case for a FlowField:CalcFormula = count("Error Message" where(Context = const(true), "Context Record ID" = Rec.RecordId()));Obviously this is pseudo and wouldn't compile, but the Context Record ID is a standard field (ID 10) on the standard table Error Message (ID 700), so improved support for the built in error handling system would be an immediate benefit of introducing Record ID as valid content for FlowFields.
RE:
We are using nested groups to organize simplify our access structure Microsoft made nested groups many years ago, and it has been a huge succes for managing many groups with many users. Microsoft should keep supporting this - or else it will be an administrative hell to have all these flat groups with no dynamic connection between them
RE:
This is needed to use the App
RE:
One of the first things our customers complain about when migrating from Windows client
RE:
Would be great to also provide a way to print item number labels with barcodes for each BOM component that goes into the production order.We see this need for an assembly operation where all materials are tagged with a non-serialized barcode (with item id) as the finished good is assembled. Not all items may have a barcode assigned when it’s received into the warehouse. Barcoding each component while executing the order for a higher level assembly simplifies the process.
RE:
Yes, this is a must have feature. Will also request the following to be available on the PFE ScreenViewing a list of quality orders that were created for all routing operations before the current operationBeing able to click on a failed quality order from previous step to examine the cause of the failure and the associated non-conformance
RE:
Hello, is this included in the 10.0.43 release?
RE:
ChatGPT says that this used to be an option previously in Dynamics 365 when "Financial Reporting" was called "Account Schedules". It said in the Row Definitions "Show" column, instead of just yes/no etc...it had the option to "Show Amounts per G/L account". If this is true, it needs to be brought back. Maybe this is a Hallucination.