Skip to main content

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.

Labels

Labels:

Comments

  1. Ramakrishna ChallaJuly 2, 2014 at 8:49 PM

    I've added my code as below:

    FormStringControl fsc;


    fsc = DlgFd.control();
    fsc.mandatory();

    It is giving red wavy on that field of the dialog but dialog is allowing us to OK with out the fields value.

    Can you please suggest me.

    thanks in advance.

    ReplyDelete

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)     {     ...
Post a Comment
Read more

Dynamics AX 2012 ValidTimeState tables and form changing view from current to all

Valid Time State tables are new i AX 2012 a gives the developer the possibility to easily create tables that hold e.g. current setup data for various purposes, and at the same time keeping a "history" of the changes of the data in the table. For more reading: http://msdn.microsoft.com/en-us/library/gg861781.aspx I was tasked with doing a setup table with rates for calculating Vendor Bonus and I chose to base this a valid time state table. The customer asked for a button on the form, where you maintain the vendor bonus calculation setup data, so you could toggle viewing "Current setup" or "All setup" records (changing the view from actual to all records and vice versa in the form). I found that you can not change the ValidTimeStateAutoQuery property on the form data source in a form at run-time. It simply does not change anything, so I came up with the following solution: A boolean class member in the classdeclation method of the form: boolean ...
Post a Comment
Read more

ProcessGuide framework

I was tasked with developing a custom "process" for printing ad hoc labels in the Dynamics 365SCM WHS app. WHS process guide - development docs Reading the great articles from 1clickfactory (starting point  https://www.1clickfactory.com/blog/advanced-whs-mobile-device-development-part-1-process-guide-framework/) gives a good starting point. Especially Edgaras' tip on running  SysExtensionCache::clearAllScopes();  in a runnable class after introducing a new step/pagebuilder class combination  is VERY useful. And of course Microsoft's own documentation ( https://docs.microsoft.com/en-us/dynamics365/supply-chain/warehousing/process-guide-framework ) also helps. However, I wanted to chip in with a couple of things. Extending WHS base enums If you extend the WHSActivity, WHSWorkExecuteMode or WHSWorktransType base enums with new options it is a good idea to run a database synchronization when you are done with extending them. Otherwise you might be frustrated to find, th...
1 comment
Read more