Finance | Project Operations, Human Resources, ...

Answered

Hide/disable control on report parameter form/dialog

(2) Share

Report

Posted on by CD-28072126-0

117

Hello All,

I want to hide/disable control on report parameter form/dialog form. I found this article: How to disable/hide report parameter on form from 2015 that explains how to hide a control. The verified answer was "You can decorate the parm method in the data contract with [SysOperationControlVisibilityAttribute(false)]". I tried that like this:

[
    DataMemberAttribute('Detailed'),
    //SysOperationLabelAttribute(literalstr("@SYS8811")),
    //SysOperationHelpTextAttribute(literalstr("@SYS20687")),
    //SysOperationGroupMemberAttribute('Order'),
    //SysOperationDisplayOrderAttribute('10'),
    //SysOperationGroupMemberAttribute('NoSuchGroupAsOrder'),
    SysOperationControlVisibilityAttribute(false)
]
public boolean parmDetailed(boolean _detailed = detailed)
{
    detailed = _detailed;
    return detailed;
}

It did not hide the control. Instead, the control was displayed as the last control on the form instead of at its usual position.

Another suggestion was to use the SysOperationGroupMemberAttribute method with a group that didn't exist. I tried

[
    DataMemberAttribute('Detailed'),   
    SysOperationGroupMemberAttribute('NoSuchGroupAsOrder')
]
public boolean parmDetailed(boolean _detailed = detailed)
{
    detailed = _detailed;
    return detailed;
}

and it worked. However, that looks like a hack to me.

Yet another suggestion in another article showed that you could add code to the build method of the UI Builder class like this:

DialogField detailedField = this.bindInfo().getDialogField(custAgingReportContract, methodStr(custAgingReportContract, parmDetailed));

detailedField.visible(false);

I have presented 3 ways to accomplish my goal. Which is the recommended way, and if it is the first one (SysOperationControlVisibilityAttribute(false) on the parm method), why didn't the verified answer work for me? If the recommended way is not one of these 3, feel free to share.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

Martin Dráb 237,882 Most Valuable Professional on at

Like (2)

Report

Moved from Integration, Dataverse, and general topics forum to Finance | Project Operations, Human Resources, AX, GP, SL forum, because your question must be about either AX 2012 or D365FO. Please tell us which one.

The reason why the attribute is ignored may be that the visibility is controlled by another logic a UI builder class.

Another idea is opening the SSRS report and switching the Visibility property of the parameter to Hidden.

Was this reply helpful? Yes No
CD-28072126-0 117 on at

Like (2)

Report
Thanks for your answer.

The software is Dynamics 365 F & O 10.0.42.

We copied the Customer Aging Report temp table and various classes associated with it. I did not notice anything in the UI Builder class that might have affected it, but I will look again. I see that DialogField::addDialogField has this code:

// check visibility if (!memberInfo.parmVisible()) { return null; }

I will see how memberInfo is populated for my parameter.

Now you have introduced a fourth method - open the SSRS report and set its Visibility property to Hidden. It works. I like it the best. It's the simplest method. So, is there a recommended way, or should I just do whatever works?

Was this reply helpful? Yes No
Verified answer

Raj Borad 1,428 on at

Like (1)

Report

Hi,

My recommended approach is to use the UI Builder class method:

DialogField detailedField = this.bindInfo().getDialogField(contract, methodStr(contractClass, parmDetailed));
detailedField.visible(false);

This gives you full control over visibility and behavior dynamically at runtime. The attribute [SysOperationControlVisibilityAttribute(false)] should work, but it is known to behave inconsistently — especially if the UI Builder class exists or the framework decides control order differently. Using SysOperationGroupMemberAttribute with a fake group name is a hack and not recommended. Go with the UI Builder, as it’s the cleanest, safest, and fully supported way to hide or disable controls.

Was this reply helpful? Yes No
CD-28072126-0 117 on at

Like (1)

Report

I forgot to mention that I don't need the flexibility. For example, I don't need to hide the control at particular times or from particular users. I always need the Detailed version of the report, so I initialise Detailed to Yes and hide it so that it can't be changed. For that reason, I will go with Martin's answer, but if I can accept more than one answer I will accept yours too.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Hide/disable control on report parameter form/dialog

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Hide/disable control on report parameter form/dialog

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates