Hi,

I have added some multiselect fields to a WIT for my project. In VS they render correctly, but in the web view the dropdown section is only using half the length of the field to display the check box entries.

Also this only seems to be happening on the tabpages. I have other multiselect fields in the main section of the record which render correctly and use the full length of the field.

Any thoughts?

-p

hi

i am also facing same issue,for me In VS and web view the dropdown section is only using half the length of the field to display the check box entries


Please Suggest where i went wrong.

thanks,

Manju

Which browser are you using? Can you post an example of a string that's rendered incorrect?

I am also seeing my values cut off in Web Access. I tried it in both FireFox and Internet Explorer 11. It seems to happen irrespective of whether or not there is a tab control in the WIT layout.

Here is a screenshot of what I see:


These values are supposed to read "Value 1", "Value 2", and "Value 3".

Update: It appears as if I had set it up wrong. The WIT to include the brackets around the values appears to have fixed the issue.

Hi,

@clcruItch, I did not run any test, but from the way items are rendered, my first impression is that the values are not enclosed in brackets in the suggested values. Could that be the case?

As an example, XML should be something like this:

<FIELD name="SomeFieldName" refname="Your.Namespace.SomeFieldName" type="String" reportable="dimension">
<SUGGESTEDVALUES expanditems="false">
<LISTITEM value="[Value1]" />
<LISTITEM value="[Value2]" />
<LISTITEM value="[Value3]" />
<LISTITEM value="[Value4]" />
</SUGGESTEDVALUES>
</FIELD>

Regards

Stéphane

Hi, we also got this issue, and also for us its only on tabpages, any fixes?

Are the values enclosed in brackets as Stéphane suggests?

MOlausson wrote:

Are the values enclosed in brackets as Stéphane suggests?

Yeah the control is working great, just it's layout is truncated..

Ok. And you are using the latest release (1.2.2.0)?

Was using 1.2.0.0, now upgraded to 1.2.2.0 and still got this issue.

As you can see, Its affecting only tabbed controls:

Thanks, then I know how to repro. I will take a look and get back.