on 2010 May 31 8:14 AM
When running a package which is updating the dimension (make_dim task) we run into a problem.
The sql tables are all updated, but the xml & dim files of the dimension on the server are not updated.
Therefore when new idu2019s are added in the dimension, they will exist on the backend, but they will not show
up in the current view. Because this current view is based on the dim & xml files.
Step to reproduce: Run the package and check the timestamp of the dim & xml files afterwards.
Your updated dimension members dont display in the current view because after dimension updation from backend, you must export them to the File Server location. BPC Client basically downloads these excel sheets in local machine and uses it in the current view.
You may modify your above SSIS package such as to add a task to get the data from mbr<<dimension>> table from the database in the SQL Server DB Engine and update the dimension excel file located in the server.
You may also add a task to update the template version of the appset to make sure that the updated dimension sheets gets downloaded to all the client machines.
This will help the current view get the updated members of the dimension.
Hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Our SSIS package has already been modified to contain an export from the Auto_MbrCUSTOMER table to an Excel file
D:\BPC\Data\Webfolders\MY_DATABASE\MY_CUBE\Reports\Export_CustomerDIM.xls
But I suppose this isn't the right file. Could someone tell me which exact file needs to be modified and how?
Do I need to update CUSTOMER.DIM and CUSTOMER.XML in D:\BPC\DATA\Webfolders\MY_DATABASE\SYSTEM FILES?
Kind regards,
User | Count |
---|---|
8 | |
5 | |
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.