Ok, basically what I'd like to do is have an Excel template that contains a table of data in a range; then have an Action Button the user can click that will extract this Excel table and use it as the source of a TI process...
Now I know it's possible to pass individual Parameter values to TI, but is it possible to pass an entire range from Excel, and have TI trawl through each row of data...?
cheers,
Matt
Defining Excel as a Data Source?
- Steve Rowe
- Site Admin
- Posts: 2464
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Defining Excel as a Data Source?
The normal way if doing this would be to export the range as a flat file and then launch the TI. You could use the TM1Tools option for this rather than an action button.
I don't of anyway to do exactly what you want, though I think that some of the products in 10 do something like this under the hood.
I don't of anyway to do exactly what you want, though I think that some of the products in 10 do something like this under the hood.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Regular Participant
- Posts: 167
- Joined: Wed Mar 30, 2011 11:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: XL2010
Re: Defining Excel as a Data Source?
Thanks for the advice... actually another thought - how about sending string values to a Data Entry Cube , referenced by ClientID and LineID dimensions (eg the template could have 1-100 lines)... the TI process could then pickup the ClientID as a parameter, then load their data from this cube.
...would this work?
Matt
...would this work?

Matt
- Steve Rowe
- Site Admin
- Posts: 2464
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Defining Excel as a Data Source?
That approach would work but you would have to watch out for the data volume when DBSing over your network.
You'd need to clear your data entry cube out after you processed the data since if you get less rows next run you'll have an issue.
You'd need to clear your data entry cube out after you processed the data since if you get less rows next run you'll have an issue.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Regular Participant
- Posts: 167
- Joined: Wed Mar 30, 2011 11:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: XL2010
Re: Defining Excel as a Data Source?
Yes good point re: clearing out the cube... otherwise I was thinking of flagging each entry after it has been processed (so TI will skip over them next time), and incrementing the LineID in the user's template... this is in the event we need to keep an audit trail of entries or something 

- Harvey
- Community Contributor
- Posts: 236
- Joined: Mon Aug 04, 2008 4:43 am
- OLAP Product: PA, TM1, CX, Palo
- Version: TM1 8.3 onwards
- Excel Version: 2003 onwards
- Contact:
Re: Defining Excel as a Data Source?
It sounds like it might not be appropriate given your use case, but you can use Excel spreadsheets as an ODBC datasource. If it interests you, there is some mention of it in this MSDN article, or you can google to find lots of other examples and tutorials.
Take your TM1 experience to the next level - TM1Innovators.net
-
- Regular Participant
- Posts: 167
- Joined: Wed Mar 30, 2011 11:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: XL2010
Re: Defining Excel as a Data Source?
thanks, that is an interesting idea... but like you said, may not be a robust solution in our case 
