Feedback by UserVoice

Colin Barrow

My feedback

  1. 6,616 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

    Colin Barrow supported this idea  · 
  2. 24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Colin Barrow supported this idea  · 
  3. 11 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
    Colin Barrow commented  · 

    Also, I'm not the OP of this question but didn't want to start my own question which would largely be a duplicate of this one

    An error occurred while saving the comment
    Colin Barrow commented  · 

    I've just started with PowerQuery in Excel 2016 and would prefer an option to use SQL rather than PowerQuery's own syntax. So instead of:

    let
    Source = Excel.CurrentWorkbook(){[Name="Table3"]}[Content],
    #"Changed Type" = Table.TransformColumnTypes(Source,{{"Who", type text}, {"What", Int64.Type}})...

    I would prefer to put:

    SELECT [Sheet2$].[Who], [Sheet2$].[What], [Sheet1$].[Why]
    FROM [Sheet2$] LEFT JOIN...

    Pre-Excel 2016, I use a VBA macro to achieve this using ADO. PowerQuery looks like it can achieve most of what I need without VBA and ADO but I'd like an option to write SQL directly rather than learning PowerQuery's own syntax or manipulating the GUI

    Colin Barrow supported this idea  · 
  4. 56 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
    Colin Barrow commented  · 

    For a worksheet, BeforePaste and AfterPaste events would be useful as well

    Colin Barrow supported this idea  · 
  5. 808 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Great suggestion – thanks again for taking the time to put it on this site and for the thoughtful followup comments. This is pretty related to some other work we’ve got going and already has a fair number of votes, so we’ll work on getting plans in place now and hope to get started on this soon.

    Thanks,
    John [MS XL]

    Colin Barrow supported this idea  · 
  6. 3,379 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Colin Barrow supported this idea  · 
  7. 1,485 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks very much for your votes. And to those who took the time to fill in the survey, thank you! This is a brief update to let y’all know that we’ve started work on this feature request along with the one on changing numbers to scientific notation.

    - Urmi [Msft]

    Colin Barrow supported this idea  · 

Feedback and Knowledge Base