Connection issues with Microsoft Office are sometimes inevitable but many errors can be resolved using the Diligent Cube Updater, which is found via the 'Analyze' tab in the Diligent user interface.
Common Use Cases:
- You encounter a Microsoft based error message while working in the file
- You refresh the cube, but the data does not appear to have the most up-to-date changes
- You want to utilize a template from another project and apply it to a new project
Resetting the EBM Connection in your File
If you encounter a Microsoft based error message while working in your EBMOfficeBridge.xlsm file (i.e. a cube file) and have been unable to rectify the error through a simple restart, try running your file through the Cube Update in Diligent.
- In Diligent, click Analyze on the left.
- Scroll down and click the Cube Update option as seen below
-
Step two should bring you to the screen outlined below. From here, choose the file you would like to update.
- Wait for your file to process. The status will display as Upload Success when the file is ready.
- Click the Download icon on the right to download a fresh and updated version of the cube file. NOTE: You will need to replace the previously saved version with this newly downloaded file. The new file will save to where your default location has been set for internet downloads.
- Once you open the new file, you will need to refresh the cube. This can be done by navigating to the EBM Office Bridge ribbon in Excel and selecting 'Refresh All Cube(s). You can also perform a refresh by right clicking on any pivot table within the file and select 'Refresh'NOTE: If you are performing the cube updater for purposes of reusing a pre-existing template from another project: if the field names are not 1:1 between both projects, they will drop out of the report and need to be replaced with the relevant field in the new project.
This should have resolved any issues, but if it did not please send us a message for further support. OR navigate to the following article for additional Cube Updater Troubleshooting tips.
Comments
0 comments
Article is closed for comments.