Feedback by UserVoice

Pat Babcock

My feedback

  1. 934 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for supporting this feature. We won’t be able to in the near future, but we understand that it would be a nice improvement. Even though it seems like a straightforward idea, it is quite complex since named ranges can be dynamic, meaning that the range is calculated when the workbook is calculated.

    We’ll continue tracking votes for this suggestion.

    Pat Babcock supported this idea  · 
    An error occurred while saving the comment
    Pat Babcock commented  · 

    Would be useful!

  2. 6,615 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Wow.

    Thank you to all those participated in our survey. What an amazing number of responses, many of them with very deep content. We’re processing the over ten thousand responses(!), and already appreciate the time so many of you took to answer with passion and experience.

    Please know this survey is used to help influence various topics – both on Python as well as other related topics that the comments started to bleed into. Given the passion, I want to be clear this remains an area of exploration for us, without any specific timeline.

    We’ll provide updates as we progress on this feature request.

    Thanks!

    Ashvini Sharma
    Lead Program Manager
    Excel

    Pat Babcock supported this idea  · 
  3. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Pat Babcock supported this idea  · 
  4. 1,864 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Pat Babcock commented  · 

    Well, after over 4 years, it's clear that they aren't going to change this behavior. As entertaining as I find the constant stream of comments and supplications, it's time to unsubscribe from this useless list...

    An error occurred while saving the comment
    Pat Babcock commented  · 

    Please, MS: Fix the scientific notation on import issue. If for no other reason than to shut these guys up...

    An error occurred while saving the comment
    Pat Babcock commented  · 

    @Ccis Bmkh: Yes,yes - we all saw your brilliant YouTube the first time you posted it earlier the same day. We're all thoroughly amazed by your brilliance, and how you stumbled upon a concept absolutely none of us could possibly have conceived of- particularly since we crave a behavior that allows numbers to remain numbers. You can stop now. Thanks.

    An error occurred while saving the comment
    Pat Babcock commented  · 

    @Anonyzak spake thusly: "i'm sure there are some statistician/scientists who DO use Scientific Notation"

    <hand raised>

    Excel is the "Engineer's word processor". Statistically, there are huge numbers of engineers using Excel, and we are pretty much all adherents to Scientific Notation by nature of the data we play with. HOWEVER, I'm also one of the early respondents to this thread: Excel should not convert numbers on import - especially since, in converting to SciNot, they drop significant digits. The number import (and entry) behavior should be user-selectable, both globally and in the import dialog... And as one of those respondents back ... What? Four years ago, now? ... I am equally frustrated that this seems to have been going absolutely nowhere at a very high rate of speed. It's almost as if UserVoice is for input to politicians...

    An error occurred while saving the comment
    Pat Babcock commented  · 

    YAY!

    Pat Babcock supported this idea  · 

Feedback and Knowledge Base