Skip to Content
0
Former Member
Nov 26, 2015 at 02:48 PM

EPM Add-In formatting issue after MS15-116 update (KB3101499, KB3101543)

68 Views

Hi BPC Community and Experts!

We are facing formatting issues in existing reports since the installation of MS15-116 security update (KB3101499 in Excel 2013 or KB3101543 in Excel 2010).These reports were working perfectly until the update was installed last week.

We would like to know if any of you had the same problem and if you could tell us if you found any solution or workaround.

The issue is described as follows: when user selects only base members in page filter, formatting for base members is not applied correctly - see sample below. Borders are not applied for base members:

When user selects non-base member in page filter, borders are drawn correctly (since EPM Add-In uses "Calculated Member" format in this case as it did for non base member lines in previous image):

In Formatting Sheet, both formats (calculated and input members) are exactly the same. This formatting scheme was working perfectly before the update.

One more important detail: the issue only happens if a report uses "EPMDimensionOverride" for any dimension (CostCenter, in this case) - or if it uses dimensions linked by property (in this case CostCenter = Unit.CostCenterId to select data linking Unit and CostCenter dimensions).

Environment details:

- EPM Add-In 10 SP23
- Microsoft Office/Excel 2013 and 2010 (tested on both, same issue in same report).

We we have already tried:

- updated EPM Add-In to SP24: didn't solve the issue;

- removed *.exd files in "C:\Users\%User%\AppData\Local\Temp\Excel8.0": didn't change anything;

- removed KB3101499, but issue still happens: it seems there are a number of KBs installed in November 11th 2015 included in MS15-116 pack, and some other might be the cause.

SAP Notes we have checked:

- 2219713 - EPM Add-In Issues after Microsoft Update KB3085502: basically MS15-116 is the solution update for the issues described in this note, so previous issues have been solved but now we face a new one.

Links:

MS15-116: https://support.microsoft.com/en-us/kb/3104540

Thanks in advance!

Regards,

Luigi Laporte