Forum Discussion
4 Replies
- AustinKQrew CommanderIf you want to lock it after submission on the form you could set a rule that prevents the fields from being edited once there is a valid date created, set the rule to be when Date Created is not equal to blank that it marks the fields read only. The date created is not there until the record is saved.
This would however prevent them from editing it at all after saving, even if they forgot to include the right information.
One thing to keep in mind is if the users have the ability to grid edit or import they will be able to get around any form rules you put into place. Form rules are only active on forms. - ChristopherWhe1Qrew MemberHow are users "submitting" their Approval Entry? Is it a Record Creation, or do you have a URL Button that marks a checkbox or kicks off a Pipeline? Something else?
------------------------------
Chris Wheatley
------------------------------- SehunJooQrew Member
Users submit their approvals through an input form that adds a record, so Record Creation yes.
In my case, the biggest reason why I've locked the record editing is because I would like for users to press a specific button that will allow editing + delete all former received approved notices for that approval request.
------------------------------
Sehun Joo
------------------------------- BlakeHarrisonQrew CaptainOk, I admit, I'm getting a bit confused. Can you outline the structure of your tables/relationships involved in this approval process and answer the following:
- Where are you wanting to put this Update button
- What records do you want it to Edit/Add/Delete
- What is your user's process (step-by-step)
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------