Thanks, Nigel. I couldn't figure this out for sure, until today, because I'm working with a new Apptio implementation, and I also work from several offices, some with poor network connections. And sometimes I get the error, and sometimes I don't.
But at least I've managed to recreate the 412 error now. Today, I'm working at a site with a wireless network, and I guess the network is fairly good today, because I didn't get the 412 error that I got yesterday, repeatedly.
So, some final advice from me, in case it helps anyone:
- In a situation where this is working fine, I deliberately introduced some import errors to my upload file. I picked one of the Numeric columns, and in Excel changed it to an Accounting format (which substitutes "0"s with "-"s, Apptio can't handle this scenario). And then when I uploaded the file again, I got the 412 error.
- Sometimes I didn't see any import errors, but then I switched the month in TBM Studio to the one for the file I was uploading - and then I saw the import errors.
- The file uploaded fine. (I have to remember to wait until the upload reaches 100%, and then pause for a bit, before flicking over to the Import step - I'm a bit too impatient when it comes to moments like this!) To check, I can download the file again, and it will show the 'digested' form of the data. Skipped rows are left out, numbers are converted to strings if they were overridden as Labels, etc. The original file isn't kept by Apptio, so in a way, this is a good data check to see what was stored - if I really do want to check.