Locking row item/s from deletion for select few roles on the basis of another boolean formatted line

Hi ,

I need help in the below query,

I have a boolean formatted line item in source module published on a dashboard. As soon as the Boolean flag is marked “True” by ‘Role A or Role B’, the expectation is for corresponding row item/s to get locked from deletion for all roles except Role A & B on all the dashboards(two) wherever the row item is reflecting with a delete flag.

Please suggest a solution apart from 'giving selective access to Role A & B to the requisite list or source module' since the delete action is dependent on the boolean flag

Thanks,

Ajinkya

Accepted answers

VIGNESH.M

Hi @Ajinkya

Try this

Step 1: Create a separate Line Item(LOCK) for Locking the List items from deletion

In my example, Module name - Account Deletion

Step 2: Publish this LOCK Line Item to a dashboard and give access to Role A and Role B to this dashboard, so Role C/D cannot access this dashboard and delete the accounts.

Step 3: Create Read/Write Access drivers as shown in the module

Step 4: Use this read/write access driver in the Delete line item, so the locked account won't be available for the deletion for any user.

Step 5: Create a Delete action based on the Delete Line item and publish it your dashboard

Step 6: Create another Delete action based on the LOCK line item and publish it in the Lock Account dashboard.

In this way, locked accounts cannot be deleted except the user have access to the LOCK Account dashboard.

I hope this will solve your issue

Thanks,

Vignesh M

All comments

JaredDolich

@Ajinkya

The confusing point for me about your use case is when you say "locked from deletion".

Are you trying to prevent a list item from being deleted or trying to prevent a cell from being edited?

Cell Editing Prevention

This use case sounds like an example of how Dynamic Cell Access could help.
The Boolean that is manually set would trigger the DCA Boolean to be "read only". this would prevent the cell from being edited.

List Item Delete Prevention

In this example, the manual Boolean set would trigger the Boolean in the system module that controls the list.
When you run your delete action, only the list items that are not reflective of the Boolean on the dashboard would be deleted.

If interested, let me know which your trying to do and I'll pull together a visual example for you.

prabhu

Hi Jared - I am interested to know your approach, can you give some visual example 🙂

Ajinkya

Hi Jared, I am trying to prevent list item deletion.

VIGNESH.M

Hi @Ajinkya

Try this

Step 1: Create a separate Line Item(LOCK) for Locking the List items from deletion

In my example, Module name - Account Deletion

Step 2: Publish this LOCK Line Item to a dashboard and give access to Role A and Role B to this dashboard, so Role C/D cannot access this dashboard and delete the accounts.

Step 3: Create Read/Write Access drivers as shown in the module

Step 4: Use this read/write access driver in the Delete line item, so the locked account won't be available for the deletion for any user.

Step 5: Create a Delete action based on the Delete Line item and publish it your dashboard

Step 6: Create another Delete action based on the LOCK line item and publish it in the Lock Account dashboard.

In this way, locked accounts cannot be deleted except the user have access to the LOCK Account dashboard.

I hope this will solve your issue

Thanks,

Vignesh M

JaredDolich

@Ajinkya

@VIGNESH.M has a very good solution if that is your use case.

My idea was to use a system module that would be based on business rules you define, an assumption that your use case was a little more simple. If I'm wrong, let @VIGNESH.M and I know. We'll get you to the finish line.

Step 1: Create the system module. This is where you will set up your business rules that determine what can and cannot be deleted. You can put this on a dashboard, or keep it in the background so the user cannot override your decisions. In this case I have a simple rule. If Keep Me! is True then you cannot delete this county.

Step 2: Create a delete list action. that deletes counties that are marked for deletion. Notice only the counties that meet our business rules will be deleted, thus "locking" the other list items.

Step 3: Add the delete action to a dashboard so users can remove the list items that meet your business rules.

See the results:

Quick Links

Can you help?

Unanswered questions

Request for Workflow Design: End-User Report Finalization & Stakeholder Notification with Version Co
Hi everyone, I'm looking to design a workflow and would appreciate your input or guidance on how to set this up effectively in Anaplan. So, the goal is: Once end users complete their data input, they should be able to trigger a process that: Notifies stakeholders via email with a link to a report. The report includes: A…
OAUTH 2.0 vs Google Sheets Extension
Hi, My org is looking to explore leveraging Google Apps script to extract data out of Anaplan and update already built templates in Google Sheets. We use the Anaplan Extension currently but find it crashes often with the amount of tabs, data, etc. Has anyone used both Anaplan OAUTH 2.0 API and Goolge Apps Script to write…
Exports with anaplan using informatica connector
I'm trying to execute an Action to export data with the use of a Mapping in Informatica. But it gives us null rows .If we export directly from Anaplan , the export file has all the rows filled. Both exports have same number of rows but in the informatica export the values appear as blank. This issue is with only some…