5638, AB#614485, changed setup page so that assembly is not in the production group.#5692
5638, AB#614485, changed setup page so that assembly is not in the production group.#5692insightworks007 wants to merge 4 commits intomicrosoft:mainfrom
Conversation
|
@insightworks007, setting the test generation rule for assembly output and doing a post preview on Assembly Order gives a bad used experience. 'Quality Inspection Test' window opens behind preview window with empty values Secondly, there are no 'Create Assembly Rule' nor 'Edit Assembly Rule' on the 'Quality Inspection Test Generation Rules' page |
@ChethanT The post preview issue is going to require someone from Microsoft to make a change in codeunit 900 "Assembly-Post" as a pre-requisite such that the "PreviewMode" variable is accessible via the posting event, or another way of making it accessible. This flag in that codeunit is set via SetPreviewMode, but there is no way to retrieve it during the Codeunit::"Assembly-Post", 'OnAfterPost' event. |
@ChethanT This doesn't seem as simple as removing 'Assembly' from the application area on the field with assembly inside of the production group. Approach 1 is I could remove the instructional text for those groups in addition to removing the assembly application area in the one field. |
I have opened bug AB#616805 to track this issue. |
Apart from moving Assembly to its own group, you can also hide the Production by controlling the visibility of the group. This is how it would look for Essential user |
|
Replaced with PR #6071 to handle recent object renames. |








Replaced with PR #6071 to handle recent object renames.
Summary
Changed the setup page to separate the assembly setting into it's own group, out of the produciton group.
As clarified in teams, did not make changes to the wizard since there is a re-design of the wizard soon.
For a similar reason I did not add a link to start the wizard under the same presumption.
Work Item(s)
Fixes #5638 ( AB#614485 ).