Disappearing values

[AmbPin]

Hello,
I have a simple mapping cube to map dimension elements when integrating data from a very granular system to a more consolidated legacy reporting system.
My mapping cube [MyMapCube] has two dimensions [MyGranularDim] & [Measure] which has a single string element called "Note". This cube will map [MyGranularDim] elements to [MyConsolDim] elements as shown below.

MyGranularDim	MyConsolDim
GA	CA
GB	CA
GC	CB

I have created a picklist cube to enforce data integrity so that people can only select valid elements from [MyConsolDim] when updating the mapping cube. The rule for my pick-list cube looks something like this:-
SkipCheck;

Code: Select all

[Measure:'Note', '}PickList':'Value'] = s:
  'Subset:MyConsolDim:}MappingSubset'
;

This all works fine. The problem I am having is that occassionally I go to [MyMapCube] and there appears to be no data there, however if I restart the server then the data values are back. Has anyone else encountered this behaviour and, if so, found a fix?

Many thanks.

[jim wood]

Why are you using a control subset in the picklist? This may have something to do with it, but to answer your question I've not seen this before, but then again I've never used a control subset in a picklist cube.

[AmbPin]

Thanks for your input Jim.
I tend to use control subsets for anything that the "system" depends upon so it protects even admins from changing things inadvertently. I would have thought that if using a control subset was a problem then the picklist would not have worked at all, on the other hand you could be completely right. I will make a duplicate without using a control subset and see if the same happens.
The values had disappeared again this morning, however I have found that if I un-load the cube (right-click in the explorer) when I then open the cube the values have returned.
Need to look at doing this programatically at the end of overnight processing me-thinks.

[BariAbdul]

I tend to agree with Jim on this one ,If this is reoccurring regularly,Why don't you try creating normal subset and use in the picklist definition rules ? Thanks

[Wim Gielis]

Hello

I often use control objects for subsets and it just works fine.
I do not have a clue why you tend to have values that disappear.
Do you have a regular SaveDataAll (just guessing) ?

[tomok]

I don't know where you guys are getting the idea the OP is using a control subset. There is no object that I know of in TM1 called "}MappingSubset". Clearly he created this thing himself (unless this is some new beast from PM). The only strange thing here is he used the } character as part of the name. I think it's common knowledge that you can't have picklists on attribute cubes and attribute cubes start with the } character. Perhaps it's related, perhaps not. The only way to know is to re-create the subset and don't use the } character in the name to see if that fixes the problem. Seems like a pretty simple test to me.

[declanr]

I think it's common knowledge that you can't have picklists on attribute cubes

In 10.1 (some versions of it at least) you actually could have picklists on } cubes and those picklists could be defined via a picklist attribute (so an }ElementAttributes_}ElementAttributes... cube/dimension) or by using a picklist cube on the } cube.
As of 10.2 they broke that functionality for using an attribute based picklist on the } cube but you can still get it to work by building a picklist cube for your } cube.

[jim wood]

I don't know where you guys are getting the idea the OP is using a control subset.

TM1 treats any object starting with a } as a control object. That's why it is hidden from the users and only admins can see them. I raised this as a possible issue with there being possible viewing right issues for other users. It was only a shot in dark as I had never seen this happen. Wim kindly confirmed that this shouldn't be the issue. So hey ho. I'm glad it made you a happy for a milli second.

[tomok]

TM1 treats any object starting with a } as a control object.

I guess that really depends on your definition of a control object. If by "control object", you mean it gets hidden when you tell Architect or Perspectives to hide control objects, then I guess it is. My definition of a control object is a cube or dimension, created by IBM expressly for the functionality built into the product. If you create something and just give it a "}" in it's name that is not a control object. That's like me putting a NASCAR sticker on the back of my Prius and claiming it's an official race car.

[jim wood]

created by IBM expressly for the functionality built into the product

Control object are not created by IBM. They are created by the software they bought. They are only created when certain triggers occur, for example a pick lists as mentioned earlier. They are however created starting with a } so the software knows to treat them as control objects, so therefore if you create something starting with a } the software thinks of it as a control object. So if the software defines it as a control object then why should I argue with the definition?

[AmbPin]

Thanks for all of the input.

I created the "}MapSettings" subset with a "}" so it would not normally be visible to ordinary users and less easy for admins to amend

Have created a duplicated set without the "}" so will let you know what happens.

[tomok]

Control object are not created by IBM. They are created by the software they bought.

Really? That's your argument? 'Nuff said.

so therefore if you create something starting with a } the software thinks of it as a control object.

So, if a create a dimension and call it }MyWorthlessDimension, and it does absolutely nothing, it is now a control object? Not in my book. I think the key here is that TM1 treats it like a control object as far as the UI is concerned. That means you can't delete it through the UI and you can easily hide it. That's probably because WAAAYYY back in the Applix days some programmer took the lazy route and decided to key off the } in the object name when deciding which objects to exclude when filtering control objects. That doesn't mean naming something yourself with a } makes a control object. It simply makes an object that takes advantage of the programming goof by Applix. It's a neat hack you can take advantage of but that's about it.

[jim wood]

Really? That's your argument? 'Nuff said.

It wasn't really an argument. I was simply pointing out that IBM didn't create anything on the core server side. As you pointed out yourself it was created by a lazy developer at Applix. Oh hang on, was it? Was it created by lazy Manny? I'm sure he'd love that???

So, if a create a dimension and call it }MyWorthlessDimension, and it does absolutely nothing, it is now a control object?

It's a good point. From an absolute point of view yes, from a realistic point of view, no. That's argument. I'm not wrong to call it so and your not wrong to think of it as anything else.

Putting my Admin hat on:
I'm not the one throwing strong opinions out there and telling them like fact. I only answered you in that way to see how you reacted. As usual you reacted in a way that was both aggressive and argumentative. While I think we can all appreciate a good debate. You need to think long and hard about how you address the users of this forum.

[tomok]

I was simply pointing out that IBM didn't create anything on the core server side. As you pointed out yourself it was created by a lazy developer at Applix. Oh hang on, was it? Was it created by lazy Manny? I'm sure he'd love that???

As much as I admire Manny, I doubt he built every bit of TM1 himself personally. Perhaps he had a staff of programmers? I imagine that if you could track down the personal responsible for using the "}" as the trigger for the filter mechanism, he/she would agree that it probably wasn't "best practice".

As usual you reacted in a way that was both aggressive and argumentative. While I think we can all appreciate a good debate. You need to think long and hard about how you address the users of this forum.

Jim, me disagreeing with you does not make me "aggressive". Are we so sensitive on this forum that we can't have a healthy debate? Did I call you any names or use any profanity? I simply stated my opinion and backed it up with facts. Am I absolutely correct? Probably not (even though I like to think I am always am ). Don't take things so personally.

[Wim Gielis]

I really meant adding a } in front of the object name so that it is hidden and not easy to destroy.
In the past I did not have any issue with using subsets or dimensions or cubes in that way.
So I am interested to know what is going on here for the OP.

[jim wood]

Jim, me disagreeing with you does not make me "aggressive". Are we so sensitive on this forum that we can't have a healthy debate? Did I call you any names or use any profanity? I simply stated my opinion and backed it up with facts. Am I absolutely correct? Probably not (even though I like to think I am always am ). Don't take things so personally.

I don't know where you guys are getting the idea the OP is using a control subset.

That's not disagreement it's disrespectful and aggressive. Aggression is about how you make your point. It's not about profanity or name calling. I'm not going to say anything more on the matter. If you can't see it then ah well.

[tomok]

I really meant adding a } in front of the object name so that it is hidden and not easy to destroy.
In the past I did not have any issue with using subsets or dimensions or cubes in that way. So I am interested to know what is going on here for the OP.

As am I. Being able to name a cube or dimension using a "}" in front of it (and thus inheriting special treatment) is a neat undocumented feature (otherwise known as a hack). However, I think it may open you up to other problems. I mean, who else knows what other code in TM1 simply looks at a "}" and decides to do something special with it. I have a sneaky suspicion that the OP might have encountered one of those.

[AmbPin]

Hello,
Thanks again for all contributions. It seems that my disappearing values are being caused by an overnight process which performs dimanesion maintenance which flattens the structure, rebuilds and adds new elements. None of the "real" data cubes are affected in this way, although I am not using many rules.
To make sure my pick-list values are available I have added a cubeunload command at the end of the overnight process. I might also add a viewconstruct if performance requires.

[lotsaram]

Hello,
Thanks again for all contributions. It seems that my disappearing values are being caused by an overnight process which performs dimanesion maintenance which flattens the structure, rebuilds and adds new elements. None of the "real" data cubes are affected in this way, although I am not using many rules.
To make sure my pick-list values are available I have added a cubeunload command at the end of the overnight process. I might also add a viewconstruct if performance requires.

To me your approach sounds a little risky as unloading cubes is not always as simple, if there are dependencies for example or if a user has a view open then it might not be possible to unload a cube. If data is being lost due to a dimension maintenance process where elements are being deleted and recreated then the better solution IMO would be to modify the maintenance process so that the dimension is unwound and no elements are deleted and then added back.

[AmbPin]

no elements are deleted and then added back.

Thanks lotsaram
The way you suggest is how my process works, elements are moved to a temporary bucket within the dimension and the structure re-assembled - no elements are deleted.
Sorry for not making that clear.