Comment 5 for bug 1741072

Oh, that would be because I didn't realize a test had been written for that. It's supposed to change also, the reason it was forcing those two fields to be strings was that doing so allowed them to be applied by copy templates. That didn't address the actual issue (select values are always considered strings, even ones matching ^[0-9]*$. With the change to those fields there's no need to special case those two in the conversion process. (with the added benefit that string-ified versions of templates still work with the corrected fields.)