Feedback by UserVoice

Jim Barrett

My feedback

  1. 24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Jim Barrett commented  · 

    I know this has low votes but was wondering if this is even in the pipeline and if so approximately when it will happen. I have a customer/org that uses Office 365 and they want to purchase multiple(15+) licenses for one of my add-in's from AppSource. Without changing the add-in to implement licensing (which we can do), the only way the customer can do this is for each user to have a Microsoft Account and purchase the add-in separately. This is not practical. Also, the admin cannot go to each users PC and use an admin account to purchase for them because a single user/Microsoft account can only buy 1 license of an add-in in AppSource.

    If there are any good workarounds it would be great to know. Also, great to know is an approximate time frame for when, if at all, paid add-ins will be able to be centrally deployed from Office 365 Admin.

    Thanks.

    Jim Barrett supported this idea  · 
  2. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jim Barrett supported this idea  · 
  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Barrett shared this idea  · 
  4. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Barrett shared this idea  · 
  5. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jim Barrett commented  · 

    I have subsequently found that this error also occurs if a binding range is cut/paste to a different sheet from where it was created. binding.getRange() returns the original sheet not the new sheet. The binding data correctly "follows" the cut/paste to the new sheet (using the Office Common API binding.getDataAsync()).

    Jim Barrett shared this idea  · 
  6. 61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Jim Barrett commented  · 

    Please consider in your review that ANY Excel.Run(..) call clears the undo history/buffer, even if the Excel.Run(..) is only doing READ operations on the sheet. For example, a call to get the current selected range breaks Undo -- ctx.workbook.getSelectedRange().load();

    Jim Barrett supported this idea  · 
  7. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →
    Jim Barrett shared this idea  · 
  8. 118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Feature Requests and Feedback » Add-in: Excel  ·  Flag idea as inappropriate…  ·  Admin →

    Renat, thanks for reporting this issue! We are aware of this and the bug is currently being patched. Note that the undo stack will be removed upon any “update” action occurring in the add-in. For read actions, we’ll preserve the undo-stack. We’ll let you know when this is available.

    Thanks,
    Office Extensibility Team

    An error occurred while saving the comment
    Jim Barrett commented  · 

    This is a really bad issue. Undo is a very heavily used feature of almost all Office users and especially Excel.

    This problem really limits the use of the Excel 2016 API as you can only use it in places where it is not going to make the user angry by taking away Undo on them.

    My use case is that I want to execute an Excel.Run() in a DataBindingChanged event handler. If I do this the user can't undo any changes they have made in the sheet, inside or outside of the binding range. I'm not going to implement it because, as a user, I would never use an add-in that disables Undo on me.

    Please fix this.

    Jim Barrett supported this idea  · 

Feedback and Knowledge Base