on
RE:
Also an improvement is to show all GL accounts that are missing and don't stop by the first error and just showing 1 GL account number. Please provide an overview with all GL-accounts numbers from which Business Unit.
RE:
It would be very helpful. During the calculation process it should be possible to select calculation rule via Record to include, which should be used.
RE:
I agree with Ted. This feature would enable us to identify the report that generated a particular query. Why is this important? Because, in an organization that runs 100's of Power BI reports in Snowflake, when a query is running long it is terminated by the DBA team and we need a way to identify the report that generated the query so we can fix the query (i.e., make it more efficiient)
RE:
This is really an issue causing the mrp calculation going wrong seeing the inventory of the special order as free inventory for other orders since special orders are not taking in account in the standard mrp calculation and the extra needed item will not be proposed to be ordered. This leads to stock shortages at customers. Please take this issue seriously.
RE:
Dear Microsoft Admin - your github link is incorrect.
RE:
Any update on this? Wasn't included in latest v24.This would be a massive time save for management of both Sales and Purchase price lists.
RE:
Need that too! would be wholesome if implemented.
RE:
It is perfect, that we can now use Multi-Select Option sets in Form Fields for our Marketing Forms.
If you have many Option values to choose from, the Form Design is poor though, because we can only choose the Rendering Control Checkbox for Multi-Select Option sets. Is it possible to add the Rendering Control DropDown for Multi-select Option set Form Fields. That way the user using the Form on the Website has the same UI Experience as the User using the same field inside the app.
RE:
When a field on a marketing form is required, a Dynamics user is able to set a "Required error message" in the field properties that appears if someone tries to submit the web form without completing the field. Dynamics users are able to set the error message for most form field types. However, when setting an option set form field as required, the "Required error message" field is notably missing. There's a workaround to manually set the error message in HTML, but its not very user friendly (see this post).Users should be able to specify the "Required error message" in the field properties for all field types, including option sets.