Whats the best prcocess to create an action to delete a list member in new UX
@lcapon
Yes you can achieve that functionality by using 'Delete lists using Selection' action.
Setup up the action from the Actions section of your model. And publish the action and the boolean line item on the dashboard
I hope it helps
~Anand
Hi @lcapon ,
1. Create one module with a list that you want to delete & add one boolean line item to select the member to delete
2. Create an action to delete the member you have checked via Delete from list using selection.
3. Create a process & add this action
4. Publish this process in the New UX
Note: if you are using Worksheet then you have direct option to delete the list member.Select the list & right click you can see delete item from list
Thanks
Akhtar
I Cant see this type of action?
hi @lcapon
You have to create an action in the model not in apps
You can find in the model as shown below
@lcapon ,
> Alternatively, (if it fits your requirement) you might want to publish a module (dimensioned by that list, without any lineitem) in a worksheet
> Upon right click on a list member, this will allow you to perform a few tasks out of which delete is one, as shown below
> You can select multiple list items as well using CTRL and then delete
> You need not create any action for this method
Best Regards,
vinayvm
I'm struggling to attach the process in the UX
Hi @lcapon
First you have to create an action &one process Then add action card from there you can see your process
I think there was just a little delay - its working now.
Does this work with the action type 'Delete Branch'?
No, Delete branch option will not work in New NUX.
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!
