Skip to main content

Refreshing (executeQuery) a calling form from the called form.

A feature that you often need when you work with code that is called from a form and manipulates data, is to be able to refresh the calling form to reflect the changes made, when the code has been run.

This could also be a form calling an other form, where data changes are made, in the called form, but the changes must be reflected in the calling form, when the called form is closed.

I have seen it done by making call back to a method on the calling form, that does the refresh.

You can however make the refresh from the CALLED form or code, using an args-object.

When a form calls an other form it is typically done via a menu item, and thus automatically an args object is passed to the called form.

The args object can carry a tablebuffer object that is acessed with the record method on the args object.

You can determine if the tablebuffer object is a formDataSource, and if so, you can instantiate a formDataSource-object on which you call the executeQuery-metod.

One example could be:

Form SalesTable
has a menuitembutton that calls Form SalesLine.

Form SalesTable has a display method that sums up data manipulated in Form SalesLine.
When closing form SalesLine we need Form SalesLine to re-execute the query in Form SalesTable and thus refreshing the data form SalesTable is showing.

This can be done by overriding the close method on Form SalesLine and putting the following code into it:

public void close()
{
FormDataSource fds; // Form data source object
SalesTable salesTable; // tablebuffer passed in args object

super();
// Refresh calling form data source
salesTable = element.args().record();
if (salesTable.isFormDataSource())
{
fds = salesTable.dataSource();
if (fds)
{
fds.executeQuery();
}
}
}

The above shown can also be used in a main-method on a class, so that code in the class that manipulates data shown in a form, where the class is called via a menu-button on the form.

I thought of doing it with a common object, and putting the code in a method on the GLOBAL class, to make it useable everywhere from a single line of code, but the Axapta client (3.0) kept crashing when calling common.dataSource() :0(.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

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

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