locked
Dynamic field content RRS feed

Answers

  • Here is a blog that describes how you might do this automatically using global lists: http://blogs.msdn.com/team_foundation/archive/2005/05/06/415268.aspx Here Step 3: Update the global list from an external source talks about how this is populated through a scheduled job that uses the Work Item Tracking object model to update the global list automatically.

    One way to get around Michael's point, if you don't want this rigorous checking, is to use a <SUGGESTEDVALUES> list rule, rather than an <ALLOWEDVALUES> list rule.  The latter will only allow valid values as defined by the rule (in this case from teh global list).  In the former, the rule will display the values defined in the global list in the drop down, but will allow other values to be entered too.  Another possibility is to use an <ALLOWEXISTINGVALUES> rule.

    Hope this helps,

    Thursday, December 28, 2006 10:25 PM

All replies

  • Hi Thomas

    i think we can't do this way...since process template can't be updated without importing and exporting back to TFS....Let's see other's view..moreover all the xml files in the process template are tightly coupled with the TFS..any changes if you want make..you can use the command line utility as witexport.exe and witimport.exe.....the only way of updating the workitemtypes...

    Thanks,
    Kathir

    Wednesday, December 20, 2006 5:07 AM
  •  If the change is not too often it may be of value simply to use the glimport command to update global lists as needed and point your field to use the global list for it's population. Thus no template changes are needed.

    If you need a bit more dynamic I think there was a thread and some sample code (I believe) on using global lists and updating those lists via code based on some action or event or specified regularity.

     

     

    Wednesday, December 27, 2006 12:08 AM
  • One thing to keep in mind on the dynamic global list and work items is consideration of state.

    If you remove a global list value and some work items have that value you may not realize you need to query for that value in WIQ or reports and if ever you 'touch' tht work item you will be forced to change the offending field to have a valid value from the current global list-- this may not be what you always want.

     

    Wednesday, December 27, 2006 12:11 AM
  • Here is a blog that describes how you might do this automatically using global lists: http://blogs.msdn.com/team_foundation/archive/2005/05/06/415268.aspx Here Step 3: Update the global list from an external source talks about how this is populated through a scheduled job that uses the Work Item Tracking object model to update the global list automatically.

    One way to get around Michael's point, if you don't want this rigorous checking, is to use a <SUGGESTEDVALUES> list rule, rather than an <ALLOWEDVALUES> list rule.  The latter will only allow valid values as defined by the rule (in this case from teh global list).  In the former, the rule will display the values defined in the global list in the drop down, but will allow other values to be entered too.  Another possibility is to use an <ALLOWEXISTINGVALUES> rule.

    Hope this helps,

    Thursday, December 28, 2006 10:25 PM