In R12, anyone experienced an issue with data upload disappeared after check-in the file and the table upload?

We are performing R12 upgrade and I uploaded data for Bill of IT consumption files for FY18 and FY19 for 7 tables, and checked-in at end of day around 5PM PT (2/12).  At night, I tried to check some reports, and found out that for 7 months from FY 18 the data are no longer in Apptio and have to re-upload them.  I see in the check-in history that the files are uploaded.  I will log a support ticket for this issue. 

Yes, we have also experienced this same issue.  We found that the system doesn't retain all the data when we upload multiple months in one table at the same time.  So we have to check-in the table after each month is loaded.  Fortunately for us, we don't have to load multiple months very often, so we've just been doing it one month at a time.

It happened to us while we were working in a branch once, but it was related to time settings. If you try to load the file to a table to a time period that is 'closed', then even though the check-in history shows you have uploaded the file, the result is as if no file was uploaded. At that time, we restricted our time setting to only a certain range and we loaded that file outside of the range.

So I am not sure if this is the same situation like yours. I hope Apptio support will resolve this for you soon. It's an unsettling feeling that data went missing.

Sorry about your experience. I created a ticket this morning after changes I made last night to my report disappeared after check-in. 

We did experience the same and raised a ticket; but since the same could not be reproduced, this was forgotten i guess. Hope you could find a solution which will help the whole lot of us who went through the same.

Below is the answer from support desk:

------------------------------------------------------------

The most common cause of data disappearing after uploading is when a delete operation is included in the check-in. Reviewing your checkin, we can see there were many files uploaded for the table Manual Adjustments and, at the bottom of that check-in list, a delete operation checked in as well - usually resulting from deleting backing data after an upload. This will result in unpredictable behavior and could result in lost data for the Manual Adjustments table. To avoid this issue, either use the Overwrite function or delete backing data, then check in the document, and upload new data on a separate check-in.

------------------------------------------------------------

This is really good information. I didn't know you couldn't perform "delete" and "upload" operations on the same table in the same check-in. I'll distribute this advice to my TBM team here.

We had the same issue and it was related to one of two issues. The first as @Yi-Wen Lin has stated and my workaround now includes that anytime I need to delete something I do so as a completely separate step: check out, delete, check in. The second was related to versioning. We had utilized the source system notation box within the upload step. At the time, entering notation here caused the data to 'version' so I would upload a new source table, it would appear to have been captured but it would disappear upon check in. The workaround for this unfortunately was to delete the table and recreate without entering anything in the source system box.

I did know about this issue with the delete function. We did have the same issue once. But the other time, i there was no delete done. not sure what went wrong. we just checked in all the work and re-did from the upload again.

Thanks @Yi-Wen Lin for sharing the response from Support!  Whenever we upload data, we almost always use the Overwrite function, so I'm not sure why it was behaving this way for us.

I had a similar experience when I couldn't see my data after successfully uploaded as shown in the Check In History. I repeat the upload and still couldn't see my data. I later found out that it was because it is still on the Calculation Queue. So for my case, the lesson learnt is to check the Calculation Queue first.

Please do file a support ticket for this. I've seen very similar issues lately in our R12 dev environment. Sometimes, the tables will upload fine. Other times, the uploads will disappear after check-in, and sometimes, the server will throw an "Error -402," and the upload will fail.

I've noticed that if the table upload disappears after check-in, hitting "refresh workspace" will sometimes cause the upload to appear again. Sometimes, not.

We had two additional issues with file upload and we filed a ticket.  Below are the summary from support for your info. 

1.

If you change Source System value (see screen shot) after you’ve uploaded a table, it will create a new version of the table and there will be a bug where you can no longer edit the table. The current solution is to delete the table and rebuild it.

__________________________________________________________________________________

2. It also appears the error message from file upload is not very helpful:

_____________________________________________________________________________

Sometime the error is unfortunately an ungraceful message as a result of validation being selected for the table. We have an existing ticket with our engineering team to provide a more helpful message, but that's not available quite yet. In the mean time what you can do is go to the import step and check all the validation errors that exist there. After reviewing and deeming things to be fine OR reverting the upload, fixing issues with the file then re-uploading, you can just check the table in. 

Thank you

@Yi-Wen Lin This is exactly the issue I was referencing above. We had a ticket entered with Engineering so maybe a future release will address it.