on
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.
RE:
This absolutely should be a feature. I have a balance sheet that summarizes groups of accounts. I should not have to create a separate row definition that list every single account I have in the g/l. I should be able run by balance sheet with an option to show all the accounts in the groupings/subtotals. This is a basic requirement, that lesser financial systems have.
RE:
This is absolutely a great idea! Having a json with a complex types where the 3rd party cannot do the escape of the json body is a pain atm.