One option is to leave the deployment parameter empty, then set it in the saved search install/update script instead. In fact, the script can be used to workaround any of the account-specific value issues that pop up with SDF. I wish the framework would just trust us, and let us reference something not in the project, as long as it exists in the target account.