Mapped Specify WB fields not uploading into collection

I have created a WB entry form that mimics the Specify Collection Object.
Each field is "not hidden" and available on the WB. Only one is not mapped in the WB.
I have checked the fields and they are correctly mapped, but when I enter the data into WB they do not show up in the Collection Object after being uploaded.
Here are the 3 fields that I'm having trouble with:
1) Col Obj Attribute> number39 -- Doesn't upload any data into Specify from WB.
2) Col Obj Attribute> number40 -- Doesn't upload any data into Specify from WB.
3) Determinations> yesno1 -- Doesn't upload "true/yes" or "false/no" if left blank, "true/yes" when selected, "false/no" if selected and then un-selected.

Anyone have any ideas? or similar problems and figured out how to solve them?

Thanks,

Sean

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Solved.

I quote from Tim Noble:
"The problem is that they are mis-mapped in the specify_workbench_upload_def.xml file.

You can fix it yourself by editing that file and modifying the actualname value for COA.Number37-42.

< field table="CollectionObjectAttribute" name="colObjAttributeNumber37" actualname="Number37"/ >
< field table="CollectionObjectAttribute" name="colObjAttributeNumber38" actualname="Number38"/ >
< field table="CollectionObjectAttribute" name="colObjAttributeNumber39" actualname="Number39"/ >
< field table="CollectionObjectAttribute" name="colObjAttributeNumber40" actualname="Number40"/ >
< field table="CollectionObjectAttribute" name="colObjAttributeNumber41" actualname="Number41"/ >
< field table="CollectionObjectAttribute" name="colObjAttributeNumber42" actualname="Number42"/ >"

Thanks Tim. It worked and I love it!!
To anyone who copies this... please remove the space after "<" and before ">".

Sean