Latest Contributions by DavidSolari

I ran into a similar issue in the past and unfortunately there wasn't a workaround. To my understanding FeatureSetByName must take name of the table as a string literal or it'll create an error. I have to assume there's some hacky pre-processor nonsense that goes on with this function, either way you'll just have to type out the right name for every rule. If you're writing the rule multiple times you might want a script tool that uses Add Attribute Rule to save some time. As an aside, that method of getting the max ID isn't optimal for large datasets, even with an index on the ID field. You may want to look into combining a database sequence with NextSequenceValue to get a new ID in constant time. ... View more

As a one-line function: def sub_to_zero(a, b): return a - b if a > b else 0 ... View more

You can do this by: Looking for a text file with config options in a known location and populating those values in the tool's validation section if they exist, and  Writing the user's chosen values to said config file if no default value exists. For the location of the file, the best practice for Windows is to use a folder with your team's name in the %APPDATA% folder, which is set per user. You can get the config file like so: import os from os import path folder = path.expandvars("%APPDATA%\\AlfredSoft") if not path.exists(folder): os.mkdir(folder) config_path = path.join(folder, "tool_config.json") # Or whatever format works for you if path.exists(config_path): with open(config_path) as config: pass # Work with the file here!  As for creating or editing the config file, you should do that in the tool itself or in the validator's updateParameters method, depending on how you want to lay your code out. If you get reading working then writing shouldn't be much more work. ... View more