App-to-App Permissions/Relationships
Hello! I am building my second app and trying to tie it into my first -- it feels like it wants to be separate because the users who will primarily use this app are from another department, but there is a lot of collaborative/universal information in my existing app I'd like to be able to share between the two apps, though there's too much in my initial app that the other department should not have access to, so creating a whole separate space for them and feeding in the pieces I do want shared access to feels like the best way, rather than bring them into my existing app and cull back their access. To that -- A) does that logic track properly? And B) Do they need a relationship to every table I watn them to access, including grandparent tables? I wanted them to see some grandparent info, and I notice when I run tests using them as a user, that since they're not in that other app, they only see throughput from the table-to-table access, and anything that's generating off a grandparent table just won't throughput for them, which is really surprising to me. Thanks! My view, and then that user's view side by side:
VLOOK-UP (relationschip)
I’ve made in QB a table, where we can search on a specific code and he will give the other related masterdata (out of backtable). Problem statement: The problem here is , he can only work with 1 code (80737797) - to reflect the related masterdata, so in case we have multiple codes , we are currently not able to reflect all the codes via this way. So in this case , Code 80748492 & 80830493 aren’t able to be reflected via the “Related masterdata”-fields. Is there any potential way to have this done within the same “record ID / Line” ? Is there any other opportunity to have the same outcome , but with another workaround. I know we can go for multiple record ID’s. But this I would like to avoid as it will create confusion for our partners. Many thanks !
I need help creating a snapshot field in a unique parent-child relationship.
In my app, there is a relationship between two tables, call them Table A and B. In table A, there is a column called batch date. For this field, we would like to create a new field based off of it called initial batch date in the same table. This would essentially be the first value that was inputted in the batch date field (that field has end users inputting a value often). From the research I have done, the best way to preserve original values is using a snapshot field. From what I understand all I have to do is add a lookup field to the child table, then create a new field for a snapshot that effectively references this lookup field. The problem is in this relationship, table A is the parent and table B is the child. How would I create a snapshot field for table A in this situation? So far I added the lookup field in table B, then I created the snapshot there, and then added it as a summary field in table A to reference the original snapshot. This did not seem to give the desired result. Any suggestions? Open to anything. Sorry if it is not super clear as I am only a few months experienced in QB. Thanks,
Child Table Field Question
I have a table called "Crane Inspections" that is the child table of a table called "Open Crane Deficiencies". I am trying to have a way to put in deficiencies (up to 4 in one form) that are either existing (noted on previous inspections and still an issue) or new. On the crane inspection form, a crane is selected from a multiple choice field, 23 different questions are completed, then deficiencies (existing or new) are annotated at the bottom. I have a way that this works now, but I am trying to make better. Right now, I have a pipeline that triggers when a new crane deficiency is put in the form (also up to 4 new ones) and creates open deficiency records in that parent Open Crane Deficiencies table. Our maintenance department goes and works on correcting the deficiency, then closes it out which deletes the record from that table. Meanwhile, on the crane inspection form, that previous open deficiency option will no longer be one on the existing crane deficiencies multiple choice field (the table-to-table relationship field). My more ideal end state is rather than have to manually select up to 4 existing deficiencies every time an inspection is completed, I would like for the up to 4 fields to be automatically populated with the existing deficiencies from the parent table. Then some way for the inspector to confirm those are still deficiencies, or enter new ones in as I have before. Please let me know if there is any clarification needed. Any help would be greatly appreciated!Can you summarize a status for a record that has multiple child records?
I have a parent table (Requests) and a child table (Activity Log) - each Request can have multiple Activities. I am trying to get a summary of the Status logged in each activity to get an understanding of the current status of the Overall Request.SWEET CONNECTIONS: The Scoop on Relationships
What Is Sweet Connections? Sweet Connections takes you on a learning journey with Miss Cone, the owner of a frozen dessert store. Through her story, you’ll learn foundational concepts like creating relationships, importing data, building formulas, and more. Each module is packed with practical tips that will help you apply these skills to your own apps. How Does Sweet Connections Work? The course is divided into four engaging modules: Cuppa Foundations: Learn the basics of app setup, including creating tables and understanding relationships. Scoop Techniques: Master advanced features like formulas, snapshots, and data imports. Topping Triumph: Explore summary fields, conditional dropdowns, and reporting tools to gain deeper insights. Cherry on Top: Bonus tips and tricks, including best practices for naming fields and maintaining data accuracy. Why Take This Course? Building relationships between tables is essential for creating efficient apps that work seamlessly with your data. By completing this course, you’ll gain skills that will save time and make managing your organization easier. Start Building Relationships Today! We offer this course in three formats. Choose your preferred learning style: On-Demand Training: Access this course anytime at Quickbase University. Semi-Private Training: Join other customers in an interactive session where you build alongside an instructor. Private Training: Contact your Account Executive or CSM to schedule a session exclusively with your organization.
Limit Relationship Choices based on another field..
So I have a table, Purchase Orders. That table is a one to many child of Jobs. It's also a one to many relationship of Daily Reports. Daily Reports is also a child of Jobs. What I want is for user A to login, and enter 5 POs, and link them to Jobs. Then, user B logs in and clicks the "Related Daily Report" field and it's limited to ONLY the jobs selected by user A. Is this possible?
