Skip to main content
BOOK A DEMO

Search

List actions - popup-window with data-input-option

Answered
Christoph Käferböck
  • Created

It would be great to have the possibility to give list actions some input data via a popup-window.

Example: there is a bulk-list action for multiple selected items "update Responsibility". If the user clicks this action, a popup should show up where the user should be able to enter a text or number or - in best case - select a value via lookup-field. The entered or selected value should be used als update-value for the field "Responsibility".

0

Comments

5 comments

Date Votes
  • Christof

    Hi Christoph
    You could create an additional custom NewForm with just specific inputs on it to update these values.
    The List Action opens this NewForm with small width in right panel, the user selects the value and press a button which saves the value into a variable and closes the form (probably best into window variable to still have access outside of form). Then continue by List Actions looping and updating the selected items with the value from the variable.

    Hope it's explained well enough to understand...

    Another approach could be to open the ootb SP item details pane to bulk edit values on selected items (but all metadata can be changed there by the user)

    Or do you think there should be a specific bulk edit form feature in skybow's Solution Studio?

    0
  • Kilgore ServiceAccount
    • Edited

    Christof:

    Another approach could be to open the ootb SP item details pane to bulk edit values on selected items (but all metadata can be changed there by the user)

    Or do you think there should be a specific bulk edit form feature in skybow's Solution Studio?

    These (2) points/questions seem related to a scenario I've been trying to determine how to best handle within Skybow...or whether not to involve Solution Studio.

     

    The Scenario:

    1. We are in a Document Library, which maintains Construction Contract Drawings. There could be 10 or 300.

    2. The end user starts by bulk drag n' drop uploading Drawings with similar metadata sets.

    3. After each batch is uploaded, those files are all selected and the default Properties CMD button is selected, which allows the user to add metadata to all of the files.

    [I have been weary of altering the default Edit Form, for Doc Libraries, in Skybow, because I am unsure of exactly how it effects the ootb ability to bulk update metadata. I feel like my experience has been that editing the default Edit form in Skybow causes for the bulk metadata function to be lost.]

    4. If necessary, Quick Edit or single-select Properties can be used to further add metadata that is specific to singular files. 

    -

    5. Then comes 'Revision Management'. (Lets say mid-way through a project, 30 of 100 Drawings are updated...)

    6. I am still thinking through ways to best handle this, in an intuitive way, and only mention it because it seems like it could related to this discussion.

     

    Another approach could be to open the ootb SP item details pane to bulk edit values on selected items (but all metadata can be changed there by the user)

    To add one tid-bit to this... If you do not bring the Edit Form into Solution Studio, within the List View, you can use 'Edit columns' to choose which fields the user can alter, and 'Configure layout' to apply basic JSON formatting.

     

     

     

    1
  • Christoph Käferböck

    Hi Christof,

    thanks for your idea.

    It doesn't work for me for following reason:

    If I select more items of a list the list action runs the same routine for every item. 

    I would need a chance to set a variable at the first run that tells "first run" an then opens the input form as you mentioned.

    In all following items an just an update-action should run with updating the field in the selected item and prior saved in an global variable.

    This "first-run" variable can't be a global variable as I see no chance to reset if before the first run or after the last run...

     

    0
  • Christof

    You can run List Actions in context of Current list instead of Selected items. This will start only one action execution (not for every item), opens just one form, sets variable once and the you can use the [[@SelectedItems]] placeholder to loop on it for the updates.
    There is a similar sample described (for document generation - not for bulk update) which could help: How to generate a document based on metadata of selected items in List Actions

    0
  • Christoph Käferböck

    Works perfectly! Thanks for your support.

    1

Please sign in to leave a comment.