RSS

How to Enable/Disable fields in a dialog

20 Feb

You can enable events for your dialog objects by overriding the method dialogpostRun:

public void dialogPostRun(DialogRunbase _dialog)
{
;
super(_dialog);

// allow to call the event methods of this class (e.g. fld900_1_modified() method)
_dialog.dialogForm().formRun().controlMethodOverload(true);
_dialog.dialogForm().formRun().controlMethodOverloadObject(this);
}

Then you can create event methods on your dialog fileds like fld900_1_modified() where you can address other components in the dialog, and modify their properties.

public boolean fld900_1_modified()
{
FormStringControl control = dialog.formRun().controlCallingMethod();
boolean isFieldModified;
;

isFieldModified = control.modified();

// every time the employee id is changed, update the employee name
if(isFieldModified)
{
dlgFldEmplName.value(EmplTable::find(control.text()).Name());
}

return isFieldModified;
}

You will also need to make sure that the control “Employee ID” gets the same control ID as used in the event method name (). This should be done at the time of adding the control to the dialog. Please see below:

protected Object dialog(DialogRunbase _dialog, boolean _forceOnClient)
{
;
dialog = super(_dialog, _forceOnClient);

// Add a new field by explicitly specifying the field id.
// This field id is used to create the field event methods (e.g. fld900_1_modified()).
dlgFldEmplId = new DialogField(dialog, typeid(EmplId), #dlgFlgEmplIdFieldNo);
dialog.addCtrlDialogField(dlgFldEmplId.name());

dlgFldEmplId.init(dialog);
dlgFldEmplId.label(“@SYS81251”);
dlgFldEmplId.helpText(“@SYS81251”);
dlgFldEmplId.value(emplId);

// verify that the field name generated by the system is correct
if(dlgFldEmplId.name() != #dlgFlgEmplIdFieldName)
{
throw error(strfmt(“@SYS79285”, dlgFldEmplId.name(), #dlgFlgEmplIdFieldName));
}

// Add a new field and let the Dialog framework to do all the work by assigning the field id and initializing the control since there are no event methods for that field.
dlgFldEmplName = dialog.addFieldValue(typeid(EmplName), emplName, “@SYS54564”, “@SYS54564”);
dlgFldEmplName.enabled(false);

return dialog;
}

Then you can get the value of fields using this method :

public boolean getFromDialog()
{
boolean ret;

ret = super();

// get the values from the dialog in order to save them in SysLastValue (using pack() method)
emplId = dlgFldEmplId.value();
emplName = dlgFldEmplName.value();

return ret;
}
verify whether a correct employee id has been specified

public boolean fld900_1_validate()
{
FormStringControl control = dialog.formRun().controlCallingMethod();
;
// verify whether a correct employee id has been specified
return EmplTable::checkExist(control.text());
}

The pack and unpack methods are used as following:

public container pack()
{
// pack the employee id and employee name and save them in SysLastValue
return [#CurrentVersion, #CurrentList];
}

public boolean unpack(container packedClass)
{
boolean ret;
Integer version = conpeek(packedClass,1);
;

switch (version)
{
case #CurrentVersion:

// get the employee id and employee name values from the container that has been saved in the SysLastValue record
[version, #CurrentList] = packedClass;
ret = true;
break;

default:
ret = false;
}

return ret;
}

Finally, in the main method :

static void main(Args args)
{
SETutorialDialogControlEvent seTutorialDialogControlEvent = SETutorialDialogControlEvent::construct();
;
// show the dialog
if (seTutorialDialogControlEvent.prompt())
{
// if OK is pressed, run some code (in that case, run() method should be overriden in the current class)
seTutorialDialogControlEvent.run();
}
}
Where SETutorialDialogControlEvent is defined as following:

public static SETutorialDialogControlEvent construct()
{
return new SETutorialDialogControlEvent();

}

As you can see the macro #dlgFlgEmplIdFieldNo is used to assign the ID to the dialog control.
Overriding the event methods (e.g. modify, validate, selectionChange) on dialog controls is not as straight forward as it is on form controls.

 
Leave a comment

Posted by on February 20, 2012 in X++

 

Tags:

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

 
axhowto

Blog about ax with sample codes, tips and tricks.

GM Dynamics Blogs

Transform IT with Digital Trasformation and Social Innovation

Ms. Dynamic Millennial

Unboxing Microsoft Dynamics 365 for Finance and Operations

DynaD365Power

Exploring the new vision of the Power platform

Dynamics Vision 365

The FinOps pulse

Breaking Bong

I write when no one is watching

ErpCoder

Microsoft Dynamics 365 Business Management Solution Enthusiast

Dynamics 365 Finance

Dynamics 365 Finance & Much More.

Microsoft Dynamics AX

“ANYONE WHO STOPS LEARNING IS OLD, WHETHER AT TWENTY OR EIGHTY.” —HENRY FORD

Sumit Potbhare

Dynamics 365 for Commerce

iotsolution.se

This is your site about D365 (Finance and Supply Chain Management), IoT (Internet of Things) and HoloLens

Omni 365

Dynamics 365 Finance and Operations Blog

DIY D365

Power Platform Done Your Way

Azure Integration services for Dynamics 365

Azure Integration services for Dynamics 365 Unified Operations, Logic Apps, Azure Functions, REST

%d bloggers like this: