Data in reference tables can differ across environments, which directly leads to have different primary key values of same reference data in the tables across environments. But, knowing this fact, still some Appian applications use primary keys of reference data as constant, for example primary keys of workflow statuses are referenced using constants rather than their text value. If while deploying or during data migration, primary key changes, then code written using those constant references may break.
What is the best approach to code for above use case?
Discussion posts and replies are publicly visible
I just use environment-specific constants for this. It causes us no major problems. I still remember trying to deal with this back before environment-specific constants were even an option - that could be a real nightmare. In comparison, now it's a breeze.