CRM Control setVisible() only shows Label

(0) Share

Report

Posted on by Community Member

Hi,

I was trying to show/hide controls on CRM form(onload) using Xrm.Page.getControl("controlname").setVisible(true). But I can see only label not the control.

Is there a way to make it work with field label position top?

Workaround:

1) This happens only when controls are set "visible by default" false, if we set this to True and set control visibility to false, it works fine.

2) Set field label position is set to side, it works.

As per my requirement I needed them to work with field label position top.

Appreciate your inputs!

-Shanker

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Karsten Wirl 4,477 on at

Like (0)

Report

Hello Shanker.

Please can you add a screenshot to visualize your issue?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

thanks for your response. first image label set as top.

if label is set to left

Was this reply helpful? Yes No
Karsten Wirl 4,477 on at

Like (0)

Report

Thanks for the screenshots. Have you worked with the Browser console to check for errors on your onload event?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

There are no error in console.

same form works fine with labels left side. This is not for this form. It is behaving same for all the forms :(.

Was this reply helpful? Yes No
Karsten Wirl 4,477 on at

Like (0)

Report

Really interesting.

What happens, when you enter data in the field, save and open again?

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Control is not present on the form. We can't reach the control, tried tab as well.

I ended up using unsupported script for now:

var curElement = document.getElementById(controlname + "_d");
if (curElement != null)
curElement.style.display = '';

Was this reply helpful? Yes No
Suggested answer

MAJBlackburn 80 on at

Like (0)

Report

We had this exact issue, our current solution is to turn off legacy form rendering, but since this is a 2011 to 2016 migration, that has its own set of risks (mostly having to re-test a couple dozen other pages on a compressed timeframe). I'm very tempted by the unsupported approach, honestly, even though it means getting a waiver from the client. The "turbo" forms have not been a great experience so far.

Was this reply helpful? Yes No