Customer experience | Sales, Customer Insights,...

is this the formContext version of foreach?

(0) Share

Report

Posted on by Community Member

Is the upgrade from Xrm.Page version I found elsewhere?

                    formContext.ui.controls.forEach(function (control, i) {
                        if (control && control.getDisabled && !control.getDisabled()) {
                            control.setDisabled(true);
                        }
                    });

And if I wanted to limit this to just the attribute controls, how do I use this feature I found in the documentation:

formContext.data.entity Attribute.controls

Tia

I have the same question (0)

All responses (3)

Answers (0)

LeoAlt 16,331 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi partner,

About the difference between "formContext.ui.controls" and "formcontext.data.entity.Attribute.controls", you could refer to the following picture.

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/clientapi-form-context

Actually, they have the same function. ui.controls could get all the controls on the current page and entity.attribute.controls could get the controls on the current entity form.

If you only want to get the attribute controls in entity form, you could use formContext.getControl() to do actions on controls.

Best Regards,

Leo

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Good reference! Bad news is that I'm not someone who understands the statement "non-entity bound attributes." Good news is that I think what I'm after is the other thing.

So what I understand you are saying is that to avoid everything but on-form attribute controls the syntax is like:

formContext.data.entity.attributes.forEach(attr, i)

...attr.controls.forEach(ctrl, j)...

where most of the second forEach will handle only one control.

NOTE: I tried doing the setDisabled on the attributes and nothing happened, probably because attributes are not controls.

thanks again

Was this reply helpful? Yes No
Suggested answer

LeoAlt 16,331 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi partner,

Actually your understanding is correct.

In "forEach" cycle, you could handle only one control. And the reason why "setDisabled" is useless is that you should get the control to set disabled not attributes.

As we can see in the doc, we should use formcontext.getControl().setDisabled();

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/controls/setdisabled

Hope it helps.

Best Regards,

Leo

Was this reply helpful? Yes No