SharePoint
Feedback by UserVoice

Alex Terentiev

My feedback

  1. 194 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Alex Terentiev shared this idea  · 
  3. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    Alex Terentiev shared this idea  · 
  4. 2,430 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Alex Terentiev commented  · 

    Please, consider next enhancements to Field Customizer (and Modern List UI):
    1. implement modern Quick Edit mode
    2. Add "edit" mode to field customizer
    3. Make field customizers (both view and edit modes) applicable on forms, panels, quick edit mode, etc.

    Alex Terentiev supported this idea  · 
  5. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SharePoint Dev Platform » SharePoint Framework  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Alex Terentiev commented  · 

    Thanks for the quick answer. But I still have concerns about that...

    onRefreshCommand is not called (I believe, event is not fired) when the command is executed.
    It is called if the command is rendered for the first time OR some list item (row) was selected.
    It means that I can't change the title or any other property after (or simultaneously) with onExecute.
    The second thing - there is no way to mark command as 'pressed'. And I believe that it could be very in-demand case for ISV's...

    about onDispose - I've tried it. Just simple
    @override
    public onDispose() {
    console.log('Command Set is disposing');
    }
    and tried to set breakpoint inside.
    But the breakpoint has never been hit. Maybe I just didn't try correct use case to make it happen :)

    Alex Terentiev shared this idea  · 

Feedback and Knowledge Base