Seems like this should be doable, but Im struggling to figure out the right way to accomplish...
<<over-simplifying my example>>
I have a table with Status and Notes. When Status is 'Closed', the Notes field should not be editable. Easy, I added the necessary formula on the Editable? setting for the Notes field. That works fine.
Now I have an action button that should do two things... (1) change the Status field to 'Open' , and (2) Prompt for Notes entry via the Input function. This is where Im stuck.
Without any additional modifications to the Notes field Editable? formula, the user gets the pop up but the Notes field is still locked from editing. (I would assume because the Status change does not become official until I fully complete the action).
Anyone have an idea on how I can modify that Editable? formula so it allows the input like I want it?
Try separating the Status change and the Notes edit into separate actions and kick them off using a Grouped action.
Thanks. That does in fact in work. For some reason I had it in my head that the INPUT function didnt work as part of a grouped action.
Does anyone know a way to do it inside of a single action though? I was hoping to maintain the change as an Atomic (all or nothing) operation.
Since I do not know a way to implement your desired data changes in one action to ensure they stay atomic, here is one idea that may or may not work for you. (you also need to create a custom Add action to show the original Form because the default Add button also shows the newly created Form)
Create a custom form with just two fields, Status and Notes. The user has to manually change the Status to Open before the Notes can be changed.
The Status actually can be changed back to Closed after the Notes is changed if the user for some reason chooses to do so and to ensure it stays Open, you can create a bot on change events with a step to force the Status to Open which will be fired if the before and after values of the Notes are different.
I do not know your exact requirements but, users with malicious intent can re-open the form and set the Status to Closed. With user roles, depending on exactly what you need, you could implement something further...
Well good luck.
Appreciate the suggestions @TeeSee1 . Gonna try to get creative and see what I can come up with.
User | Count |
---|---|
28 | |
14 | |
4 | |
3 | |
3 |