Jump to content
Server Maintenance This Week. ×

Lock data entry after the entry is made


This topic is 6708 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi

I need some help that I hope someone can help me with.

I have a field "Type" where I have a value list added to holding "Type 1" and "Type 2".

The user may change from "Type 1" to "Type 2" but when the "Type 2" is selected the field needs to be locked for futher changes.

Do anyone have an idea on how to calculate this?

Thanks for any help.

Link to comment
Share on other sites

Hi, Peter

make the field "Type" an autoenter/replace with this calc:

Case(

Type = "";

Let([

$$Type=""

];

"");

Type = "Type1" and $$Type ≠"Type2" ;Type;

"Type2" &

Let([

$$Type="Type2"

];

"")

)

BTW: if someone deletes contents of the field "Type", he could change from Type2 to Type1( or whatever else if the validation of the field isn't setted to "member of value list")

Link to comment
Share on other sites

I changed my mind...due to the limitations that I said to you ...

So, I think that is better this solution.

Make a new calculated text field, let say: TypeLocker, with this calc:

Case(

TypeLocker = "Type2";"Type2";

Type = "Type2";"Type2"

)

and change the calc of the autoenter/replace Type field to:

Case(

not IsEmpty(TypeLocker);TypeLocker;

Type

)

Link to comment
Share on other sites

The holding FIELD needs to be locked from further changes? So it can't be changed from Type 2 back to Type 1? Or do you want the RECORD locked if Holding = Type 2 so no changes can be made to ANY fields within the record (such as posting month-end)? Someone may need to change that field! And someone may even need to change that record (under unusual circumstances). I guarantee Type 1 will be changed to Type 2 by accident. So if you use Daniele's method, you'd better allow modification by SOMEONE within the calc.

Another option is to use Access Privileges. You can apply field-level access, restricting changes if Type 2 to only certain personnel by using Extended Privilege Sets. It depends upon 1) how important is the lock and 2) have you established access privileges (which I highly recommend)? If you wish to go this route and need assistance, let us know. :wink2:

LaRetta

Link to comment
Share on other sites

Hi raybaudi

Your idea work as I want/need it to work.

I made the extra field and added your calculation - the entry of data to the first field is now locked when type2 is selected.

Thanks.

LaRetta, as always you take it a little futher. It was not needed for this as all the other fields may be changed after the selection of type.

But thank you.

/

Jens Peter

Link to comment
Share on other sites

Peter,

happy that that calc solved !

BTW: if you wish that any choose of that field couldn't be modified, make the calc of your field "TypeLocker" exactly the same of the field "Type":

Case(

not IsEmpty(TypeLocker);TypeLocker;

Type

)

So, if someone chooses "Type1", that will be his final choose !

Link to comment
Share on other sites

This topic is 6708 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.