Home Dashboard Directory Help
Search

Master Data Services - Numeric fields arbitrary maximum of 7 Decimals unnecessarily restrictive by DeeBeeGee


Status: 

Closed


1
0
Sign in
to vote
Type: Suggestion
ID: 795497
Opened: 7/31/2013 4:21:35 AM
Access Restriction: Public
0
Workaround(s)
view

Description

Would it not be better to make the maximum decimals allowed for a numeric field a configurable item to allow the administrator to decide what is a reasonable in the context of the application.

After all, everyone has different needs..
http://blogs.scientificamerican.com/observations/2012/07/21/how-much-pi-do-you-need/

While there is a workaround it is quite cumbersome and not explicitly supported. An alternative method of multiplying the value by a factor to move the decimal point (eg pi = 31415.9265359 / 10000) is a sure fire way to get input errors

See thread below for proposed workaround using mds SPs and a further issue with the way numeric datatypes are defined
http://social.msdn.microsoft.com/Forums/wpapps/en-US/f30a6442-37b9-40bb-bc06-de6b30bdb641/more-than-7-decimal-places-in-a-number
Details
Sign in to post a comment.
Posted by Microsoft on 8/1/2013 at 9:35 AM
Hello DeeBeeGee. After carefully evaluating all of the suggestion items in our pipeline, we are closing items that we will not implement in the near future due to current higher priority items. We will re-evaluate the closed suggestions again in the future based on the product roadmap. Note that the article you reference states that five decimal precision is within 0.000084%. Thanks again for providing the product suggestion and continued support for our product.

-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.