Apptio for All

Hello @Anughya . ,

Can you give a little more context?  Is there a reason why you'd be uploading a file multiple times per month?  Since ApptioOne reports on a monthly or financial period basis, we don't typically recommend multiple uploads of the same file in the same month. I'm sure there could be situations where the data was updated or a mistake was made, so it's not unheard of just trying to understand the use case for your ask.

Cheers,
Deb

I don't have the answer to this, but we do upload our GL transactions and AWS tags daily. 

 Hi All,

@Debbie Hagen , @Abekan Koffi 

We generally maintain a manual Runbook where we store the file load information, how many times it's being loaded in Apptio (reason can be anything like file data was incorrect or from business we got new set of data to be updated or mistake has been made).

Now they are in process of automating this. So, that's why I'm looking for this. Is there any way we can automate this and Apptio will calculate how many times a particular file has been loaded.

You say you want to automate the process, @Anughya .

However, if you were to load the table(s) via Datalink, you could set up a group of connectors that:

1. Would update the data in whatever tables you need
2. Would also update a table with a counter of some sort, e.g. with the table name and the upload date

I need to think about this some more and see if I can prototype it. If so, I'll write an article about that. It will probably require a combination of something like Python (to gather/build the required data) and a Datalink connector group as described above.

We have such a setup (minus the log table update) for 8 or our data loads, all grouped together.

To answer your question I need clarification on what you're actually looking for.

Your saying "loaded in a particular month" This could mean many things.

1.)I upload a file, do not check it in, then upload over that file again, 2 is the number of times that file was loaded, 0 was the number of times it was checked in.
2.)I upload a file, do not check it in, then upload over that file again, then check it in, 2 is the number of times it was loaded, 1 is the number of times it was checked in.
3.)I upload a file, do not check it in, upload a file, do not check it in, revert the check out, 2 is the number of times that file was loaded, 0 is the number of times it was checked in.

4.)I upload a file many times, then check in. (Many is the number of times it was loaded. 1 is the number of times it wa checked in)

5.)I upload a file many times, then check in. Then in the same month I upload a file many times, then check in again. (Many + Many is the number of times loaded) 2 is the number of times it was checked in.

So what number are you actually looking for, the number of times you've actually uploaded a file in the system, regardless of it being checked in, or just the number of times a TABLE, has a new filed checked into the system?

There is no system table or function that can give you this answer.  (Edit: Incorrect, see @Mark Nealey 's reply) You will need to establish a process to capture it.  
Assuming that the question is how many times (and when) new raw data has been checked-in to a table, I think that @Jenny Franklin's solution is very good.  Just be aware that the Datasets table (on which the Data Expiration report is based) only reflects the most recent data load in each period.  It will not reflect how many times data was reloaded in each period.
To capture this you many want to take inspiration from @Guillermo Cuadrado's response and run a Datalink connector that copies "Jenny's table" appended to an "archive" table, so that a snapshot is saved each time the connector is run.  (I can elaborate on this if you want).  You can schedule this connector to run as often as you want, e.g. daily, but it will still not catch any data loads between runs,  only the state of things (file name and last load date/time of each table) at the time the connector is run.

The Audit log does contain pieces of this info, that's what I need my question answered as to what specific number they're trying to see.

@Mark Nealey ... assuming the OP was only interested in checked-in uploads, is there a OOTB Report in Apptio One that shows this.

@Jaitabh Jewel Sharma There aren't any out of the box reports but I'm sure I could make something with a legacy report, doing this for 1 document probably isn't that hard, essentially the check in history for a document has this info, massaging it into a useful view would be the work.  However I suspect they want this for all documents, I'd like to know the exact requirement before digging into it to deep.