FIM2010-Semi-Dynamic RCDC Operations

Like many, I have been trying to find a good method to create RCDC’s that are dynamic similar to the ones that are created for the groups and user objects where a checkbox may allow different fields to be presented. I have done some playing around with this and found a method that gives me a semi-dynamic method for having some of these controls.

As most have done, we know we can hide different RCDC objects or control whether they are read only using boolean values in our target objects. This is important as we can use these mechanisms to allow controls to be visible or not visible on demand so long as we have automatic postback set on the values.

In the example below, I am using the mail enabled boolean flag to determine whether or not the display name field is visible and required:

<my:Control my:Name=”MailEnabled” my:TypeName=”UocCheckBox” my:Caption=”Mail Enabled” my:Description=”{Binding Source=schema, Path=MailEnabled.Description}” my:AutoPostback=”true” my:RightsLevel=”{Binding Source=rights, Path=MailEnabled}”>

<my:Properties>

<my:Property my:Name=”Enabled” my:Value=”True”/>

<my:Property my:Name=”Visible” my:Value=”True”/>

<my:Property my:Name=”Required” my:Value=”True”/>

<my:Property my:Name=”DefaultValue” my:Value=”False”/>

<my:Property my:Name=”Checked” my:Value=”{Binding Source=object, Path=MailEnabled,Mode=TwoWay}”/>

</my:Properties>

</my:Control>

<my:Control my:Name=”DisplayName” my:TypeName=”UocTextBox” my:Caption=”Display Name” my:RightsLevel=”{Binding Source=rights, Path=DisplayName}” my:Description=”{Binding Source=schema, Path=DisplayName.Description}” my:Visible=”{Binding Source=object, Path=MailEnabled, Mode=TwoWay}”>

<my:Properties>

<my:Property my:Name=”Columns” my:Value=”80″/>

          <my:Property my:Name=”Required” my:Value=”{Binding Source=object, Path=MailEnabled, Mode=TwoWay}”/>

<my:Property my:Name=”MaxLength” my:Value=”256″/>

<my:Property my:Name=”Text” my:Value=”{Binding Source=object, Path=DisplayName, Mode=TwoWay}”/>

</my:Properties>

</my:Control>

You can really use this method against any type of boolean control value in the RCDC including the visible and required methods shown above. But there is also the read-only and enabled flags. Check with the controls that you’re using for the different boolean controls that you can use in this method.

Important caveats to using this method:

• Uninitialized boolean values will cause your RCDC to not render. You will get that error message that there is a problem with the RCDC at the bottom of the window and be looking at the default view (which is usually seen with the advanced view button). This has resulted in my having to create a default values workflow that ensures that all the booleans are set in new objects that come from the synchronization engine or are created using the portal itself.
• When using these methods in the create RCDC’s, make sure you are providing  a default value (as in the MailEnabled control where I have <my:Property my:Name=”DefaultValue” my:Value=”False”/> defined) as this “initializes” the values for the attributes and allows them to be used. Failing to this and you end up with the error noted above.
• Review the operation of the RCDC carefully. In some cases if a user selects an option and it removes a control inappropriately, you may end up with some data issues. This is something that can be mitigated with some post processing of course however, be aware that the RCDC changes immediately. So in the example above, if the user had changed the mail enabled to disabled with a display name value configured, that value could be lost (although it isn’t required). Make sure you test appropriately.