Planning Analytics

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information:

If the dimname subset in question is not listed among the elements in the }Subsets_<dimname> dimension it is private; that should work.

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information:

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information:

Hi Vlad,

Subsets by themselves are not public or private which is why there is no property of a subset that says so either, it is the location where a subset 'lives' that determines if a subset is public or private, hence the subset can be public, in which case you'll find it in the 'Subsets' collection of a hierarchy, or private, in which case you'll find it in the 'PrivateSubsets' of a hierarchy or a subset can even be private to a view, which can be the case in both public or a private view, in which case the subset is 'contained' within that view.

The place where subsets live is only really visible by looking at the canonical URL of such subset which you can retrieve by using a $expand against the subset's /$ref. In your case I'm imagining you are using a `$expand=Rows($expand=Subset)`, by adding the $ref as in `$expand=Rows($expand=Subset/$ref)`, you'd get the @odata.id who's value is that canonical URL to the entity and therefore will contain that `Subsets` or `PrivateSubsets` path segment which you could use to determine if a subset is public, kept private or even is specific to a view (in which case the view itself is in the path - I'll let you figure that one out;-).

FYI, there is no way unfortunately to do an expand and do an expand/$ref at the same time but if you do not include the key property in the $select TM1 v11 will inject the @odata.id to uniquely identify the entity as well. Note however that v12 in those cases injects the key property instead. As such it would be better to depend on the /$ref. If you need more information about the subset you can use that canonical URL returned by @odata.id to retrieve any additional information about the subset you'd need.

Hope this helps!    

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information:

Thanks, Hubert, I appreciate your detailed answer!

In my case, I'm trying to use a single API request to get the subset name or MDX or element list (which I believe you refer to as "a subset specific to a view") for each dimension:

Hi Vlad,

Subsets by themselves are not public or private which is why there is no property of a subset that says so either, it is the location where a subset 'lives' that determines if a subset is public or private, hence the subset can be public, in which case you'll find it in the 'Subsets' collection of a hierarchy, or private, in which case you'll find it in the 'PrivateSubsets' of a hierarchy or a subset can even be private to a view, which can be the case in both public or a private view, in which case the subset is 'contained' within that view.

The place where subsets live is only really visible by looking at the canonical URL of such subset which you can retrieve by using a $expand against the subset's /$ref. In your case I'm imagining you are using a `$expand=Rows($expand=Subset)`, by adding the $ref as in `$expand=Rows($expand=Subset/$ref)`, you'd get the @odata.id who's value is that canonical URL to the entity and therefore will contain that `Subsets` or `PrivateSubsets` path segment which you could use to determine if a subset is public, kept private or even is specific to a view (in which case the view itself is in the path - I'll let you figure that one out;-).

FYI, there is no way unfortunately to do an expand and do an expand/$ref at the same time but if you do not include the key property in the $select TM1 v11 will inject the @odata.id to uniquely identify the entity as well. Note however that v12 in those cases injects the key property instead. As such it would be better to depend on the /$ref. If you need more information about the subset you can use that canonical URL returned by @odata.id to retrieve any additional information about the subset you'd need.

Hope this helps!    

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information:

Hi Vlad,

Well, actually, using full metadata in OData, you can get everything in one response (read: both the @odata.id as well as the properties) but you'd also get the association and navigation links for any navigation properties you are not expanding so it might be a bit verbose, yet you could. In that case you would expand using the `/$ref` but you'd expand the subset but add the "odata.metadata=full" to either the Accept header or the $format query option as in `application/json;odata.metadata=full` as the value for either. Note that the default behavior is to return minimal metadata.

Omitting the name only works in TM1 v11. If you want to make your solution future proof and work with TM1 v12 as well then that no longer will work unfortunately as in that case we'll inject the key property instead of the @odata.id if you omit the key property in the select.

Hope this helps!

The only way to get it all would be a request asking for full metadata, but then you get it all ;-)

Thanks, Hubert, I appreciate your detailed answer!

In my case, I'm trying to use a single API request to get the subset name or MDX or element list (which I believe you refer to as "a subset specific to a view") for each dimension:

Hi Vlad,

Subsets by themselves are not public or private which is why there is no property of a subset that says so either, it is the location where a subset 'lives' that determines if a subset is public or private, hence the subset can be public, in which case you'll find it in the 'Subsets' collection of a hierarchy, or private, in which case you'll find it in the 'PrivateSubsets' of a hierarchy or a subset can even be private to a view, which can be the case in both public or a private view, in which case the subset is 'contained' within that view.

The place where subsets live is only really visible by looking at the canonical URL of such subset which you can retrieve by using a $expand against the subset's /$ref. In your case I'm imagining you are using a `$expand=Rows($expand=Subset)`, by adding the $ref as in `$expand=Rows($expand=Subset/$ref)`, you'd get the @odata.id who's value is that canonical URL to the entity and therefore will contain that `Subsets` or `PrivateSubsets` path segment which you could use to determine if a subset is public, kept private or even is specific to a view (in which case the view itself is in the path - I'll let you figure that one out;-).

FYI, there is no way unfortunately to do an expand and do an expand/$ref at the same time but if you do not include the key property in the $select TM1 v11 will inject the @odata.id to uniquely identify the entity as well. Note however that v12 in those cases injects the key property instead. As such it would be better to depend on the /$ref. If you need more information about the subset you can use that canonical URL returned by @odata.id to retrieve any additional information about the subset you'd need.

Hope this helps!    

Hi all

When extracting a private native view and expanding the subsets, how can we determine whether the used subsets are private or public?

The subset fields do not include this information: