Possibility for read-only data fields / lock data fields

Vladimir Popov_34229

Dear Community,

I've found some older threads here but wanted to bring it up again because I think its a simple but very effective and needed feature. 

The ability to lock data fields / set them data fields to read only.

We're building custom integrations to ERP systems and transfer data into different directions / systems.

Whenever Pipedrive is not the leading system (e.g. for customer data  fields which come from ERP) we're running into the problem that sales teams can update the data in Pipedrive but this data will be overwritten on next sync (which is correct). 

We need the possibility to lock these fields so the sales team is not even able to edit those (e.g. ERP Customer ID etc.)

I think basically everyone who works with direct data integrations is running into this.

What do you think? Any possibility to bring this discussion up again?

Best and thank you very much

 

Daniel Bachmann_45847

Hey Vladimir,

I don't know of any lock functionality. However, I have an idea that may help you. 

You can use an automation to reset the value of a field to its previous value if it has been changed.

What to do:

1. Create a trigger for "Deal updated".
2. Make the condition that any of the fields you want to lock has changed. Make sure to use OR.
3. Add an action that sets all the values for the fields you want to lock to the previos value. Make sure to select "XXX before"

Technically this doesn't prevent your users from changing the fields values. However, it resets them immediately which has the same effect.
This can be quite some work if you have many fields that you want to lock, but it does the trick.
 

Vladimir Popov_34229

Daniel Bachmann said:

Hey Vladimir,

I don't know of any lock functionality. However, I have an idea that may help you. 

You can use an automation to reset the value of a field to its previous value if it has been changed.

What to do:

1. Create a trigger for "Deal updated".
2. Make the condition that any of the fields you want to lock has changed. Make sure to use OR.
3. Add an action that sets all the values for the fields you want to lock to the previos value. Make sure to select "XXX before"

Technically this doesn't prevent your users from changing the fields values. However, it resets them immediately which has the same effect.
This can be quite some work if you have many fields that you want to lock, but it does the trick.
 

Hi Daniel,

thanks for your suggestion - this is a workaround that we are currently using.

But it has two side effects:

• If you update the data via an scheduled API import it will also revert back to the old value. My goal is that i just prevent USERS from updating the fields. But there is no filter for this. 
• If you work with Webhooks they get triggered by the Workflow since the field has technically been updated and then reverted back to original value. 

Best

Vladimir

 

Josh Lawrence

I too would love an update like this!!

I would also suggest to be able to "lock" a field from user update, but still allow the field to be editable via manager/admin/automation!