Of the two columns mentioned here, I know we have talked in other threads about the Encounter.photographerX fields, and when they get accepted or rejected. Let me know if this case is
different or any further information is needed.
For the Encounter.decimalLongitude field, I have tested the file ACW_upload_Tico_02-08-2017_07-35.xlsx on my local computer, on a development machine and as far as the trial run on ACW and not been able to replicate longitude’s absence from the feedback. I have observed this behavior infrequently with other import columns on other Wildbooks however.
As far as I can tell, the error is in the tabular feedback alone. While not ideal, closing the tab you have used for the trial and simply trying again seems to overcome it in most cases. Due to it’s intermittent and infrequent nature it is very hard to debug, but know that we are tracking it, have observed it and will apply a fix as soon as we are able.
In general, when a column is rejected because of a data issue you will still see a stub in the feedback with the cells highlighted in blue, yellow or red as appropriate.
If the column is not present in the feedback at all give it another try in a new tab or browser window. If you witness it multiple times consecutively for the same file go ahead and send me the file and I will try to replicate it.