CalculateField_management should allow Domain Description value

Idea created by friendde on Mar 21, 2017
    Implemented
    Score60
    • ian.martin
    • patel1684
    • lrafrg_bmg
    • stevemac
    • rogbak
    • friendde

    When using CalculateField_management the results from expression are the coded values if a Coded Value Domain is used on the source feature's field. Add an optional parameter to use the description value instead.

     

    For example if a field named MATERIAL has a coded value domain called MaterialType where

    Code   Description

    1          Steel

    2          Plastic

    3          Cast Iron

     

    In the current usage syntax CalculateField_management (in_table, field, expression, {expression_type}, {code_block}) if expression is [MATERIAL] then the resulting calculated value will be 1 or 2 or 3 

     

    Add an optional parameter CalculateField_management (in_table, field, expression, {expression_type}, {code_block}, {use_description}) so if the expression is [MATERIAL] the resulting calculated  value is Steel or Plastic or Cast Iron