Seeing that a document record has a name should not be taken as an indication that a file has been uploaded. The presence of a file is indicated by a document icon in the File column of the Documents list, and a non-zero value in the Size column.
I get that the fact that the record having a name should not necessarily an indicator that a file is attached. My issue here is two-fold:
1) the name of the field to hold the record name is entitled simply 'Name', which may be mis interpreted as File Name rather than Document Name; and
2) the default name of the Document after import is _exactly_ the filename, reinforcing the misinterpretation in 1)
The rest of your comments are about the alert messages in the app, and yes, I could redesign the alert interface, cache the messages, display them in a summary, display them in the web interface instead, etc. But that would be a lot of work, and all the alerts will go away when you just upload your files, so it seems like not a good thing to prioritize given all the other things I want to do with this product.
I think we are talking past each other here.
I'm NOT talking about detecting 'missing file' errors in BH-iPad, caching them, and later sending them to BH-web for reporting.
I AM talking about detecting and reporting the 'missing file' in BH-web - where: 1) there are first visible (e.g. after import); 2) there are more resources available to the user to deal with the issue; and 3) they can't interrupt a live performance (assuming the iPad is more likely to be used for live performance than is a tower+monitor+keyboard+mouse...
If I am understood. I'll drop it. It's your baby. I just think things could be improved for your users. I may be missing some consideration.
Topic: "Download Error" - missing documents (Read 18863 times)