PowerPivot resets decimals to 2 in Calc Field builder - by Ken Puls, CMA, MS MVP (Excel)

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 790155 Comments
Status Resolved Workarounds
Type Bug Repros 0
Opened 6/13/2013 9:13:03 PM
Access Restriction Public

Description

When I’m creating or modifying a measure, I don’t always get the number format right the first time (shocking, I know.)  I’ve lost count of how many times I’ve used inappropriate language in the workplace after the following sequence of events:
•	Select Currency, change decimals to 0, select no symbol… doh!  Decimals have been reset to 2!
•	Do the muscle memory thing of Currency, no symbol, 0 decimals, then realize it should be a different format.  Click Number… it’s reset to 2 decimals again!

It's small, but it’s really irritating.  It would be awesome if a selection change checked the number in the decimal box to see if it is a valid selection and preserve it if so.

I know it’s still early in the PowerPivot life cycle, and I completely understand why these things are the way they are (bigger fish to fry and all.)  The reason I bring it up though, is that building with PowerPivot is an extremely slow process today.  Everything we do seems to cause a full measure recalculation which takes a significant amount of time.  Little things like this just feel like they add insult to injury as you have to keep re-applying them, slowing you down even more.  It certainly doesn’t affect my ability to do anything or create a solution, it just makes it a more frustrating experience.

(This is PowerPivot in Excel 2013)
Sign in to post a comment.
Posted by Ken Puls, CMA, MS MVP (Excel) on 7/11/2014 at 8:22 AM
Fantastic, thanks!
Posted by Howie [MSFT] on 7/10/2014 at 4:02 PM
Our engineering team has coded a fix for this which will be available in a future release of Power Pivot.

Thanks,
SQL BI Team
Posted by Howie [MSFT] on 7/10/2014 at 4:02 PM
Our engineering team has coded a fix for this which will be available in a future release of Power Pivot.

Thanks,
SQL BI Team
Posted by Kasper [MSFT] on 6/14/2013 at 10:02 AM
Hi Ken,

Thanks for the feedback, we will look into this for a future release.

Thanks,
Kasper