Skip to main content

How to work around best practice error: "A form that is not associated with other forms should be linked to at least one menu item"

How does one work around the Best practice error: "A form that is not associated with other forms should be linked to at least one menu item", when developing a custom lookup form ?

Developing a possibility of a custom setup on the table ReqSitePolicy, that allows for calculation of "External Invent Onhand level", I added two new extended data types:

ItemSearchInventSiteId exending InventSiteId
ItemSearchInventLocationId extending InventLocationId

and three new fields:

ItemSearchShowAvailInventDataAreaId based on EDT SelectableDataArea
ItemSearchShowAvailInventSiteId based on EDT ItemSearchInventSiteId
ItemSearchShowAvailInventLocationId (based on a EDT ItemSearchInventLocationId)

to the ReqSitePolicy table.

To be able to make lookups for ItemSearchShowAvailInventSiteId and ItemSearchShowAvailInventLocationId fields based on the legal entity chosen in the ItemSearchShowAvailInventDataAreaId field (even though the currently active legal entity might be something else), I prepared two custom lookup forms for the EDTs ItemSearchInventSiteId and ItemSearchInventLocationId. The querys of the custom lookup forms have the property CrossCompanyAutoQuery set to YES.

The custom lookup forms uses the legal entity chosen in the ItemSearchShowAvailInventDataAreaId to make a crosscomapny lookup for InventSiteId and InventLocationId, clearing dynalinks and doing:

this.query().addCompanyRange(dataAreaIdCriteria);

in the executeQuery-method of the datasource of the lookup form.

However compiling the lookup forms resulted in the best practice error: "A form that is not associated with other forms should be linked to at least one menu item".

Well, to solve that problem open the lookupform in the - AOT-path:

Form / "custom lookup form name" / Designs / Design.
Set the "Style" property to "Lookup".

And poof the Best Practice error has gone away.
Labels:

Comments

Post a Comment

Popular posts from this blog

Suppressing the infolog

Supressing the infolog is often useful in D365FO when augmenting code. When augmenting code using COC (Chain Of Command), you can have new code run either before or after the code you are augmenting. This means that any infolog-messages that the standard application code does, will be shown to the user, even if your augmentation supports a scenario where there must be no infolog-messages. How do you avoid the standard application infolog-messages ? To the rescue comes temporary supression of the infolog. The suppression consists of: 1) Saving the current infologLevel 2) Setting the infologLevel to SysInfologLevel::None 3) Run your code 4) Restoring the saved infologLevel to the infolog For example a table could have a validatewrite-method that validates that you are only allowed to use 3 out of 6 options in an enum-field, and you need to allow for a fourth one. Table a - validateWrite method: boolean validateWrite() {     Switch (this.enumField)     {         boolean ret;         case
Post a Comment
Read more

Indicating mandatory field in a dialog (RunBase) class.

A classical problem is indicating that a field is mandatory in a dialog, when the field is not bound to a datasource/field in a datasource. Normally fellow developers will tell you that, that is not possible. I found a way to do this. In your Runbase-based class you can implement the putToDialog-method e.g like this: protected void putToDialog() { super(); fieldMask.fieldControl().mandatory(true); } where fieldMask is a DialogField object in your dialog. This will make the field act like it was a mandatory field from a datasource in a form, showing a red-wavy line under the field, and requiring the field to have a value. Attention: Your class has to run on the client.If you set your class to run on the server, you get a run-time error, when the fieldMask.FieldControl()-call is made.
1 comment
Read more

Dynamics ax 2012 traversing selected records in a form data source

A classical developer challenge in Dynamics AX is to enable a form button when multiple records have been selected in the form by the user. This usually involves writing some form of loop (for or while or do-while) that starts out with calling _ds.getFirst() and continuing the loop as long as _ds.getNext() returns a tablebuffer. Well things got a little bit easier in AX 2012. In AX 2012 you can use the MultiSelectionHelper class. One example is the following that I encountered in AX 2012: Can you make the customer collection letter print out run for each selected collection record in the Print/Post collection letters form (Accounts receiveable / Periodic / Collections / Print/Post Collection letters). If we ignore the possibility for setting up print destination for running each report we can do this in two steps: 1) Change the "Multiselect" property of the "MenuButton" and the "Menuitembutton" in the MenuButton in the form from "Auto&quo
Post a Comment
Read more