1 Answer, 1 is accepted
0
Hello Michael,
No surprise here, this option forces the control’s ClientID to use its ID value directly, which means that it can potentially cause conflicts with other control on the page. If there are several instances of the same naming container there can easily be a client ID naming conflict. The report detail section basically acts as repeater i.e. databound control, and if you assign Static to a Databound control, child controls in templates do not get unique IDs either, so for such cases where you rely on unique Id for child controls you have to use Predictable or AutoID rather than Static. More info about the ClientIdMode is available in MSDN.
Kind regards,
Steve
the Telerik team
No surprise here, this option forces the control’s ClientID to use its ID value directly, which means that it can potentially cause conflicts with other control on the page. If there are several instances of the same naming container there can easily be a client ID naming conflict. The report detail section basically acts as repeater i.e. databound control, and if you assign Static to a Databound control, child controls in templates do not get unique IDs either, so for such cases where you rely on unique Id for child controls you have to use Predictable or AutoID rather than Static. More info about the ClientIdMode is available in MSDN.
Kind regards,
Steve
the Telerik team