@rgolightly: What that some sort of custom field that was causing the error or a standard Panel field?