BigG wrote:
I am aiming to create a dimension worksheet directory for a TM1 server, but if I have multiple TM1 servers will I have to use a shared single location because..
TM1® saves the dimension worksheet files to the first directory listed in the Local Server Data Directory field in the Options dialog box.
Looks like you can not have multiple locations for your dimension worksheet directory unless you manually change the reference in perspectives options dialog each time? Is this correct or can I manage a better way?
Depends. What's your intention?
- To have completely different dimensions on each of the servers? If so, there's no
problem in having all of the worksheets in the one place. I'm not sure I'd be crazy about it from a housekeeping perspective, only because I prefer to keep all related files as a single "box" which can be moved around as needed, but technically it's fine. Note that you wouldn't
need to do this in this case (and I wouldn't); if the dimensions that are used on each server all have different names you could put a semi-colon delimited list specifying the folders for each server into your Perspectives dialog. The .xdis for all of the servers would appear in your list (regardless of which server they relate to) and will be opened and saved back to the folder from whence they came.
- To have dimensions which are intended to be identical and shared between the multiple servers? If so, again you can have a single folder, or you can have a delimited list of folders. However any dims which are identical and shared across multiple servers should be in just one place, otherwise you run the risk of overwriting.
- To have dimensions which have the same name but differ between servers (eg test vs production)? Don't do it. I did that for a while (having the .xdis in multiple folders, obviously; you can't have them all in the same folder) but it ended up being way too easy to for the .xdis to write to the wrong place. For those I went to maintaining them through either TI or the dimension editor. But if you absolutely must use .xdis, then I'd go for the "changing the path" approach as you work on each server.