KevinSlider
Qrew Trainee
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: Lookup and fill field values based on the content of another table
Thanks for thinking of me! I may be asking something you already tried, but perhaps you need 2 automations. 1 for add, and 1 for edit. You can ADD child records, or MODIFY child records as an action in automations. If you are trying to modify child records when they exist, you would need 2 automations, and not necessarily divided by ADD and EDIT on the conditions.... You may need to use ADD actions when table a records are ADDED, or when MODIFIED and CHILD records do not exist (easily identified via summary field). conditions would be: when record is added or modified, certain fields are edited, and these conditions are true- summary field=0, then add records via automation. the additional automation conditions would be: when record is modified and summary field>0, then update records via automation. Let me know if that helps.83Views0likes0CommentsRe: Connected Table Relationships
Hello Angel, It sounds like you may benefit from a recursive relationship in the Employee table. Employees (leaders) have child Employees. Quickbase warns you when creating recursive relationships, but they can be useful, especially in this hierarchy of Staff. I would recommend creating a leader checkbox, to easily indicate which employees are leaders and can have child employees. You can use this checkbox in form rules to hide/show the child employee section and embedded report. I would even recommend a grid edit embedded report to select the child employees at the leader level. You would have some clean up on the form for Child employees, choosing whether to allow the selection of a leader on the child, or to hide this selection if the record is indicated as a leader record. Most likely, you want to have a clear hierarchy of Leaders and employees, not a chain of Leader>Managers>Employees>Minions. With recursion, it allows for infinite chains, and you want to set quickbase up so that it limits you to leader>Employees in the chain. This leaves all your employees in one table, but defines a relationship that you may use in your associations table. You then have some options. 1. you can select the leader, and conditionally select an employee (based on 2 relationships to the associations table, the employee relationship conditional on the leader relationship) 2. you can select a leader on the association, and an embedded report link can show the employees related to that leader. 3. you can use the recursive relationship to define custom permission models. There is a lot here, but let me know if it helps.17Views0likes0CommentsRe: Stop red text, and line crossing out formula rich text, when editing on forms
Hello Gary, There may not be a way to stop that behavior, but you can consider showing the formulas on View of a form only. The behavior you describe is based off of changing conditions of fields in the formula. You could also try Hiding the field with form rules at times where the conditional fields change, but I am not sure you can get around this behavior.6Views1like0CommentsRe: Is there a way to tell when a field was created?
Perhaps you have audit logs on your account, that may be able to tell you if it was recent. You may also try to ask quickbase help to find out when a specific field was created, if they have that data in the back end. For starters, what is the field ID and is it the latest field ID created in that table, or is it somewhere in the middle? That would tell you if it is a recently created field in respect to the other field development in the application. let me know if that helps.45Views0likes0CommentsRe: Create Copies of Records through Automation
You would have to create a looping automation, but be careful not to make an infinite loop! I have been experimenting with looping automations, and they are tricky. I am trying hard to write the solution here, and I have failed multiple times. Sometimes I have one automation that will kick off the loop, causing another automation to fire in a looping fashion until the conditions are met. for instance, you can have a counter field, and every time the automation to clone the task fires, it takes the counter and adds 1 to it, triggering the next automation to clone the task, increment the counter by 1 until the counter equals the number of copies specified.3Views0likes0Comments