Fix the PRESET_INFO test bug

TBH, for now I've been using it as a debug mechanism; it should only happen if you've typed the field name wrong in the check. I'm guessing you'd rather I return None though, and optionally throw an exception within the RDM test or something? Or can I throw a more accurate exception within here, to avoid too much duplicate code?