vbs file (continuing this example, using the same sample database object mentioned above):
#Cubus definition update
bat to force an update of the outline within EV. bat file, and use the ExecuteCommand method within TM1 Turbo Integrator to run the. One could then run this script on a regular basis, or call this. vbs file to create an IE instance and pass in the aforementioned URL. For example, if you have a database object named "retail\Products Sales", the URL would look like this: It is possible to script a.
(A) For the first workaround, the URL would look something like this:
Second, if your dimension structure or security information within TM1 is changing during business hours, you would want to either:Ī) set up/use a URL command to Force Preload the database objectī) use the file to proactively update the outline at regular intervalsĬ) Provide/use credentials of a user who belongs to the Admin or DataAdmin group in TM1. Ultimately, this is an issue with TM1 and how it works with external programs requesting meta-data, so the fix will only truly come from the TM1 side, but you can implement a workaround for this problem with EV one of several methods detailed below.įirst and foremost, ensure that your database connections in EV are set to preload, this would be considered a best practice. When the end-user with security restrictions accesses the view, EV attempts to update the outline as the end-user and as the currently loaded copy of the outline as EV sees it is considered out of date, EV cannot substitute the place-holders to respect the hierarchy, and TM1 throws this error about the Parent Unique Member.
#Cubus definition full
However, this problem/error arises if EV has not preloaded a full copy of the outline, or TM1 informs EV that the outline is out of date. Normally, if a user has access to only N-level elements in a dimension and EV has a full copy of the outline as admin, there is no issue EV can substitute place-holder members to faithfully respect the hierarchy of the dimension(s) from TM1.Īs well, whenever a user accesses a view, EV checks with TM1 to determine if the currently loaded, full copy of the outline is valid, and if not, re-preloads the outline to ensure that the end-user receives the most current information available. This is by design and how EV respects OLAP defined security. When a user with element restrictions accesses a view (and thus the underlying cube), EV goes back to TM1 and asks for user-specific copies of those pieces of the outline that are restricted. Normally, when EV does a preload of an outline from TM1, this would be done under an admin-level ID providing EV with a full and complete copy of the outline. However due to the way TM1 provides outline information (metadata) to EV, this situation can lead to this error.
Within the TM1 cube-viewer it is possible to get around this issue, TM1 displays only the elements that the user has read-access to. Most often what causes this error is that mid-upper level consolidations are not available to the end user in TM1 they have NONE access within the TM1 security model.