none
Why doesn't my attribute content display on some VIEW forms RRS feed

  • Question

  • I created a new attribute "Employee Role" as a pull-down attribute, modeled off of the "Employee Type" attribute that is available out-of-the box with FIM.  It is defined as an indexed string with the following validation string:  ^(CFACC|Office Administrator)?$

    I added XML to the following 3 RCDC files by copy/pasting the XML for "Employee Type" and then replacing occurrences of "Employee Type" with "Employee Role" throughout the newly copied section of XML.

    • Configuration for User Creation
    • Configuration for User Editing
    • Configuration for User Viewing

    When I create a new user, both pull-down choices are visible in the pull-down list, and I select CFACC.  When I view the user in EDIT mode, I see both choices in the pull-down list, and the EDIT form shows that CFACC is the currently selected value.  So the CREATE and EDIT forms are working as expected.  When I view the user in VIEW mode (i.e., when I click the check box next to the user's name and click on "Details"), the "Employee Role" attribute appears, but it shows no content.  If I click on "Advanced View -> Extended Attributes", the "Employee Role" attribute appears there as well and DOES show content.

    Here's a snippet of code from the "Configuration for User Viewing" configuration file and what I did to trouble-shoot...  My initial attribute was "Role" and I thought perhaps it was a reserved word and that ultimately "Role.EnumerationString" was not dereferencing to what I thought it was.  So I created a new attribute "Employee Role" instead, but I'm seeing the same thing.  I've created simple text attributes before with no issues (i.e., content was viewable on all forms), so I wasn't sure if there's a step I'm missing here given that this is an enumerated string (pull-down) attribute.

    Employee Type:  The following code outputs content for Employee Type...
    my:Value="{Binding Source=object,  Path=EmployeeType.EnumerationString}"
    Employee Role:  The following code does NOT output content for Employee Role.  Content does not appear on the main VIEW form (i.e., if you click the check box next to the user and click "Details"), but content DOES appear if you click on "Advanced View -> Extended Attributes"
    my:Value="{Binding Source=object,  Path=EmployeeRole.EnumerationString}"
    Employee Role:  If I override the XML for Employee Role above with either of the following, it outputs content (though in the first case, the content of Employee Type is what actually outputs; in the second case, it's whatever I typed below - in this case CFACC).  So I can "force" data to output on the form in the right location for Employee Role via the XML, I just can't access the content of Employee Role via the code above in order to output "that content"...
    my:Value="{Binding Source=object,  Path=EmployeeType.EnumerationString}"

    my:Value="CFACC"

    Would appreciate any ideas on what I might be missing.  Thanks!

    Friday, April 12, 2013 8:29 PM

Answers

  • In the view RCDC what control type are you using?

    Are you using uocLabel (what I would expect in the view RCDC)?

    As for the binding have you tried leaving of the .EnumerationString? Like this:

    my:Value="{Binding Source=object,  Path=EmployeeRole}"


    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html


    Thursday, May 9, 2013 4:59 PM

All replies

  • In the view RCDC what control type are you using?

    Are you using uocLabel (what I would expect in the view RCDC)?

    As for the binding have you tried leaving of the .EnumerationString? Like this:

    my:Value="{Binding Source=object,  Path=EmployeeRole}"


    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html


    Thursday, May 9, 2013 4:59 PM
  • Hi David, yes I am using UocLabel.  I tried your suggestion of leaving off the ".EnumerationString", and it works perfectly.  Thanks so much for the suggestion!

    Ramona Balke

    Monday, June 3, 2013 1:56 PM