https://community.esri.com/t5/python-questions/database-field-editing-performance-regarding/m-p/1326569#M68544 <P>Hi,</P><P>I have a quick question regarding contingent values and the potential impacts that it may have on performance either with editing in the field or the database itself. I have a script that creates all potential combinations and adds them as contingent values. Depending on what limitations or restrictions I set, I get a varying number of possible outcomes ranging from 300 to over 1000. Here is part of the script that I have that creates all possible combinations and returns a list of strings that are then added as contingent values.</P><P>&nbsp;</P><LI-CODE lang="python">from itertools import permutations, combinations # Contingent values function def CreateContingentStringValues( Fields, Condition, DomainType, DomainCodes, Constraints, SetNullConditions, ExistingValues ): Equal, NotEqual, GreatThan, LessThan = '=', '!=', '&gt;', '&lt;' FieldIndexing = { fieldname : index for index, fieldname in enumerate( Fields ) } Combinations = None if len( Fields ) &gt;= 2: if Condition == NotEqual: Combinations = list( list( combinations( DomainCodes, len( Fields ) ) ) ) elif Condition == Equal: Combinations = list( list( permutations( DomainCodes, len( Fields ) ) ) ) elif Condition in [ GreatThan, LessThan ]: pass ValidCombinations = [] if Combinations: for Combination in Combinations: ValidateCombinations = len( set( Constraints ).intersection( set( Combination ) ) ) &lt; 2 CombinationOrder = [ Constraints[ value ] for value in Combination if value in Constraints ] SortedOrder = sorted( CombinationOrder, reverse = True ) ValidateOrder = all( [ True if any( [ a == b, a &gt; b ] ) else False for a, b in zip( SortedOrder, CombinationOrder ) ] ) if all( [ ValidateCombinations, SetNullConditions not in Combination, ValidateOrder ] ): ValidCombinations += [ Combination ] ValuesString = [ ] if ValidCombinations: for Combination in ValidCombinations: FieldValueDict = dict( zip( Fields, Combination ) ) ListStrFieldNameValue = [ f'{ FieldName } { DomainType } { FieldValueDict[ FieldName ] }' for FieldName in FieldValueDict ] StrValue = ';'.join( ListStrFieldNameValue ) if StrValue not in ExistingValues: ValuesString += [ StrValue ] if type( SetNullConditions ) is str: ListStrFieldNameValue = [ f'{ FieldName } { DomainType } { SetNullConditions }' if FieldIndexing[ FieldName ] == 0 else f'{ FieldName } NULL { SetNullConditions }' for FieldName in FieldIndexing ] StrValue = ';'.join( ListStrFieldNameValue ) if StrValue not in ExistingValues: ValuesString += [ StrValue ] return ValuesString</LI-CODE><P>&nbsp;</P><P>It works but my concern is the impact that it may have on our field editors. Any help or input would be greatly appreciated.</P> Fri, 08 Sep 2023 13:02:39 GMT RPGIS 2023-09-08T13:02:39Z https://community.esri.com/t5/python-questions/database-field-editing-performance-regarding/m-p/1326569#M68544 <P>Hi,</P><P>I have a quick question regarding contingent values and the potential impacts that it may have on performance either with editing in the field or the database itself. I have a script that creates all potential combinations and adds them as contingent values. Depending on what limitations or restrictions I set, I get a varying number of possible outcomes ranging from 300 to over 1000. Here is part of the script that I have that creates all possible combinations and returns a list of strings that are then added as contingent values.</P><P>&nbsp;</P><LI-CODE lang="python">from itertools import permutations, combinations # Contingent values function def CreateContingentStringValues( Fields, Condition, DomainType, DomainCodes, Constraints, SetNullConditions, ExistingValues ): Equal, NotEqual, GreatThan, LessThan = '=', '!=', '&gt;', '&lt;' FieldIndexing = { fieldname : index for index, fieldname in enumerate( Fields ) } Combinations = None if len( Fields ) &gt;= 2: if Condition == NotEqual: Combinations = list( list( combinations( DomainCodes, len( Fields ) ) ) ) elif Condition == Equal: Combinations = list( list( permutations( DomainCodes, len( Fields ) ) ) ) elif Condition in [ GreatThan, LessThan ]: pass ValidCombinations = [] if Combinations: for Combination in Combinations: ValidateCombinations = len( set( Constraints ).intersection( set( Combination ) ) ) &lt; 2 CombinationOrder = [ Constraints[ value ] for value in Combination if value in Constraints ] SortedOrder = sorted( CombinationOrder, reverse = True ) ValidateOrder = all( [ True if any( [ a == b, a &gt; b ] ) else False for a, b in zip( SortedOrder, CombinationOrder ) ] ) if all( [ ValidateCombinations, SetNullConditions not in Combination, ValidateOrder ] ): ValidCombinations += [ Combination ] ValuesString = [ ] if ValidCombinations: for Combination in ValidCombinations: FieldValueDict = dict( zip( Fields, Combination ) ) ListStrFieldNameValue = [ f'{ FieldName } { DomainType } { FieldValueDict[ FieldName ] }' for FieldName in FieldValueDict ] StrValue = ';'.join( ListStrFieldNameValue ) if StrValue not in ExistingValues: ValuesString += [ StrValue ] if type( SetNullConditions ) is str: ListStrFieldNameValue = [ f'{ FieldName } { DomainType } { SetNullConditions }' if FieldIndexing[ FieldName ] == 0 else f'{ FieldName } NULL { SetNullConditions }' for FieldName in FieldIndexing ] StrValue = ';'.join( ListStrFieldNameValue ) if StrValue not in ExistingValues: ValuesString += [ StrValue ] return ValuesString</LI-CODE><P>&nbsp;</P><P>It works but my concern is the impact that it may have on our field editors. Any help or input would be greatly appreciated.</P> Fri, 08 Sep 2023 13:02:39 GMT https://community.esri.com/t5/python-questions/database-field-editing-performance-regarding/m-p/1326569#M68544 RPGIS 2023-09-08T13:02:39Z