Copying subsets between users

[tcornwall]

Hello,

I am new to TM1, taking over for the current admin...so still trying to figure things out.

We have a new user that started and we copied subsets (.SUB) from another user into the data folder of thenew user. The user cannot see the new subsets, but can create new subsets in that folder. The current admin says they have done this in the past without issue.

The user has logged out of TM1 and Excel and logged back in and we only see the subset she created and other public ones, no other private ones. Also as a test, I renamed the folder that had the user created subset and had the user log off and back on and it was still there, I am guessing the subsets don't load from that folder?

Any ideas?

Again, sorry for being a TM1 noob, my only experience before this is adding accounts.

[bplaia]

Assuming you're talking about private subsets, simply copying them into the user's data folder won't work.

Inside the user's data folder there needs to be a Dimension}subs directory, and that is where you may copy the .sub files

Brian

[declanr]

I haven't done this in a while but have previously and it works fine.

From memory/educated guess though I would assume you need to bounce the server (as you would with any manual changes to the data directory.)

[Alan Kirk]

I haven't done this in a while but have previously and it works fine.

From memory/educated guess though I would assume you need to bounce the server (as you would with any manual changes to the data directory.)

Not for private subsets. Those will be visible as soon as the user logs off and back on. The client apparently reads those fresh with each login. With public ones you need a server bounce.

As Brian said, though, they do have to be in the correctly named folder. They should be in exactly the same folder as the manually created ones.

Also it assumes that they are in a dimension that the user has access to and that we're not talking about shortcuts to subsets in an application folder or something exotic like that, but to actual subsets as listed under the dimension.

[declanr]

I haven't done this in a while but have previously and it works fine.

From memory/educated guess though I would assume you need to bounce the server (as you would with any manual changes to the data directory.)

Not for private subsets. Those will be visible as soon as the user logs off and back on. The client apparently reads those fresh with each login. With public ones you need a server bounce.

As Brian said, though, they do have to be in the correctly named folder. They should be in exactly the same folder as the manually created ones.

Also it assumes that they are in a dimension that the user has access to and that we're not talking about shortcuts to subsets in an application folder or something exotic like that, but to actual subsets as listed under the dimension.

I stand corrected. I haven't dealt with users creating private subsets valuable enough to be shared for a while, anything worth more than 1 person seeing I would prefer to create as a public subset just so that you can assure both are kept in sync.

I assumed that when the OP mentioned having got the user to create subsets themselves that they would have thought to put them in the same folder.

[tcornwall]

I stand corrected. I haven't dealt with users creating private subsets valuable enough to be shared for a while, anything worth more than 1 person seeing I would prefer to create as a public subset just so that you can assure both are kept in sync.

I assumed that when the OP mentioned having got the user to create subsets themselves that they would have thought to put them in the same folder.

The copied subsets were copied into the same folder that the user created their own private subset in. I had the user log out of TM1 and even close Excel. I even went as far as renaming the folder that the subset was created and the subset still showed in the drop down for the user.

Basically the copied subsets are from a user with the same rights in TM1 and they don't show up.

I was thinking some kind of bug, since they have never had this difficulty before.

[Alan Kirk]

I stand corrected. I haven't dealt with users creating private subsets valuable enough to be shared for a while, anything worth more than 1 person seeing I would prefer to create as a public subset just so that you can assure both are kept in sync.

I assumed that when the OP mentioned having got the user to create subsets themselves that they would have thought to put them in the same folder.

The copied subsets were copied into the same folder that the user created their own private subset in. I had the user log out of TM1 and even close Excel. I even went as far as renaming the folder that the subset was created and the subset still showed in the drop down for the user.

I'm afraid that I have no idea what you're saying there.

Before assuming "bug" can you give:
- The user names;
- The name of the dimension;
- The path of the database directory for your server;
- The exact path of the original user's subsets;
- The exact path that you're copying the subsets to.

[tcornwall]

I stand corrected. I haven't dealt with users creating private subsets valuable enough to be shared for a while, anything worth more than 1 person seeing I would prefer to create as a public subset just so that you can assure both are kept in sync.

I assumed that when the OP mentioned having got the user to create subsets themselves that they would have thought to put them in the same folder.

The copied subsets were copied into the same folder that the user created their own private subset in. I had the user log out of TM1 and even close Excel. I even went as far as renaming the folder that the subset was created and the subset still showed in the drop down for the user.

I'm afraid that I have no idea what you're saying there.

Before assuming "bug" can you give:
- The user names;
- The name of the dimension;
- The path of the database directory for your server;
- The exact path of the original user's subsets;
- The exact path that you're copying the subsets to.

Under the Data folder, I went into the users folder, where the subset was created under account}subs, I renamed that file to .OLD at the end.

When the user logged back in, she still was able to use the subset, even though the folder name/path had changed.


- The user names;
A. PSauerbr
B. STIMMINS

- The name of the dimension;
A. Not sure, but FinancialReporting cube

- The path of the database directory for your server;
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data

- The exact path of the original user's subsets;
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data\PSauerbr\account}subs

- The exact path that you're copying the subsets to.
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data\Stimmins\account}subs

[Alan Kirk]

Under the Data folder, I went into the users folder, where the subset was created under account}subs, I renamed that file to .OLD at the end.

When the user logged back in, she still was able to use the subset, even though the folder name/path had changed.

- The user names;
A. PSauerbr
B. STIMMINS

- The name of the dimension;
A. Not sure, but FinancialReporting cube

OK, that's where some alarm bells start ringing. How can you not know the name of the dimension?

A subset is a collection of zero or more elements in a dimension. It exists independently of the cube or cubes that the dimension is in. When you expand the tree in Server Explorer you will see a list of the dimensions, under each of which is a node which expands to show all of its subsets, if any. You will see the same list of subsets if the dimension is used in a cube, and you expand the cube to see the dimensions.

However the key point is that the place that you find a subset is sitting right under a dimension. It's therefore pretty much impossible not to know the name of the dimension that it relates to, if, indeed, you're really talking about subsets.

Where I am going with this is... are you absolutely sure that you're talking about a subset (which relates to a dimension) and not a view (which relates to a cube, even though some of the dimensions of a view may use defined subsets)?

- The path of the database directory for your server;
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data

- The exact path of the original user's subsets;
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data\PSauerbr\account}subs

- The exact path that you're copying the subsets to.
A. \\uslv-atm1-02\d$\TM1\uslv-tm1fy\Data\Stimmins\account}subs

The paths look OK and based on this it should be for the dimension named "account" but again this is assuming that you really are talking about subsets and not views.

[tcornwall]

Hey everyone, thanks for the great feedback and suggestions.

I ended up restarting the services and the subsets showed up for the user. I guess that wasn't an issue before, and there was no need to restart the services.