Forum Replies Created
-
Posts
-
It would also be nice to know what is the latest version number.
I finally found it: the workbook contains several pivot tables with a common table as a data source. The table contains a DAX query which retrieves data from a Tabular server. In order to ensure that the pivot tables remain in sync after the data table is refreshed, I had checked the option “refresh data when opening the file”. When this option is unchecked, the refresh is carried out without errors.
I am still experiencing this same issue. Would love to find a solution.
- So after a little bit of trial and error, here are my findings which may be of interest to some others:
PU does not load PERSONAL.XLSB when opening a file to be refreshed, so no wonder it couldn’t run macro in this file. - Installed AddIns are loaded as expected. So one can store their any macro that needs to be run. I have named mine “PowerUpdateMacros.xlam”.
- But in order to run a macro in an addin, PU apparently requires the full path to it (I learnt it from the failed task history)
so in the end, here is the PU macro setting was successful in my case:
‘C:\Users\myusername\AppData\Roaming\Microsoft\AddIns\PowerUpdateMacros.xlam’!mymacroNote that the module name is not required when invoking the macro, which is different from when you run a macro that resides in the updated workbook itself.
So is it supported ? How should Macro1 in Module1 of PERSONAL.XLSB workbook be invoked ?
This was my first attempt. Unsuccessful.
I upgraded to v1.1.361, and it is okay now.
Thanks.I have updated to v 1.1.357 (W7 x 64bits) and initiated the 30 day trial period of the full version, but the issue is still there.
Is there a way to solve this slow start issue ?
- So after a little bit of trial and error, here are my findings which may be of interest to some others:
