I have two tables within the same app. One table (Table A) contains records with Status A and the other table (Table B) contains records with Status B. I want to be able to move a record from Table A to Table B based on the input (Yes or No) from a checkbox field in Table A. For example, if Table A's checkbox field is checked, then the record automatically moves to Table B. Is this possible?
That way the user could see the assigned tasks in a separate report but not be able to edit it once its in the assigned tasks table.
Again, brand new to QuickBase so I may be missing something obvious here.
We all agree. Control what users see by the reports that they use and their Role permission will control what they can see and edit.
When GM makes a car, it's the same car moving down the assembly line, not a duplicate of the car being created to drop in the next assembly stage.
You have a lot of tools to work with including form rules and role permissions.
You would be better off to rephrase your question if you are stuck in terms of controlling access to the same records by users in different Roles.
For example, a Custom Role permissions for a Role that says only allowed to edit if the Status of the record is X. You can also have any complex logic you like by making a dedicated formula field for this purpose called like [Low level Role allowed to edit?] and then the Custom Role permission is when that is checked, then users in that Role may edit.
Note that users in different Roles can be set up to have different dashboards and different tabe Home pages.
You will find that menu option under settings for the table.
You could have a checkbox that says copy to other table. Then you can have an action trigger when the record is saved and that field has changed and it is set to checked.
Then configure the actions so that each individual field is mapped to the correct field in your other table.
I would suggest that you put a report link field on your main record which will show an embedded report of all of the employees with the same employee number in your archive table. That way you can refresh the main record and see that the archived record was successfully created. Then you can delete the original record manually with confidence, knowing that the archive record was successfully created.
Note that if you do you add fields to your main record, you will also have to remember to create those equivalent fields on the archive record and adjust your Action.