Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Can we also add some more style options. There are only limited colours. The Yellow (Ambiguous) is fine on a cue but hard to read as text and too close in colour shade to the green. Its is annoying that you can have italics in red but not green for example. If you are showing lines that's are favourable/unfavorable it looks odd if one is in italics and one isn't.
is this feature already available with the latest release? Can you give a brief information about the status?
See full thread on https://www.yammer.com/dynamicsnavdev/threads/22516272095232
Thank you very much, you included this option in 900, 5704,5705 Codeunit, and helps a lot.
This would be a great fix to introduce.
It is causing quite a lot of confusion for our client when creating vendor payment journals.
I'd say it is not required. There are already controls in place to authorize purchase requisitions and manual created purchase orders through workflow approval.
From a leading supply chain management practice point of view I'd say controls shall be added prior to the MRP run. Forecast, min / max coverage groups etc. shall be authorized and reviewed.
If there is another control in place to authorize purchase orders that have been created by MRP it leads to bad customer experience and highlights a failure of controls that authorize forecast and coverage groups in the first place.
Example: Modified the same list page to page type 'ListPlus' with 2 listparts. This seems to set a fixed height on the parts (unclear how the height is defined) When working with 2 monitors and moving the page (browser tab) to another window with a smaller resolution, the size of the repeater control is changed. Putting the page back to my main monitor the size is still respected, but the whitespace between the repeater and listpart is gone. The listplus seems to take up more valuable space than a list too (e.g. the DataCaptionExpr region should be able to be hidden) For a listplus page, I would like to allocate the screen height manually across the different parts too.
This idea is highly needed to speed up the conversion of complex pages (containing multiple listparts) to be workable in the webclient.
Improving the dev experience on 'List' / 'ListPlus' / 'Worksheet' page with multiple listparts.
In RTC, we have a lot of list pages (PageType : 'List') with one repeater and multiple listparts. These pages looked ok / rendered well, all worked fine (and fast!).
In the webclient, all pages of types 'List' / 'ListPlus' / 'Worksheet' act differently, each have its own limitations and rendering troubles in the webclients (when combined with multiple listparts) and none come close to the RTC experience....
Example: A list page in RTC with 2 listparts worked fine. When using this page in webclient, the listparts randomly resize in height, resulting in my active list of the repeater to dissappear. Request would be to disable the automatic sizing of the listparts and be able to manually allocate the screen size accross the different parts.
Example: A list page in RTC with 2 listparts worked fine. When working with 2 monitors and moving the list page (browser tab) to another window with a smaller resolution, the size of the repeater is reduced to 0, resulting in my data no longer being accessible.
If the answer would be that 'List pages are intended to only contain one repeater control and not other groups / parts ...' then please provide valid alternative. List pages do contain the filter pane option, while 'listplus' seems not ...
Also see examples on https://www.yammer.com/dynamicsnavdev/#/Threads/show?threadId=422908863397888
We operate in a highly regulated industry and Lot Tracking is required. This is definitely an area needing some investment by Microsoft as it is not trivial from a cost and resource perspective. Customers will look to options other than D365 if they are expected to make significant investments where they would expect there to be existing D365 functionality.