Forum Discussion
MCFNeil
7 years agoQrew Captain
If you really want the same reporting and historical data. I'd strongly recommend you keep it all in the same app.
BUT you can modify the roles and permissions so the two teams can work in the same application. You may have to make a small modification to the setup.
If they truly are the same process, same reports, and just different teams. Use the same app, and have roles save the day.
BUT you can modify the roles and permissions so the two teams can work in the same application. You may have to make a small modification to the setup.
If they truly are the same process, same reports, and just different teams. Use the same app, and have roles save the day.
- DavidLichty7 years agoQrew TraineeThank you Matthew.
The business requirement is that they be separated. The people will now be on completely different teams with different management.
If I cannot find an elegant solution now, I can wait until the end of a fiscal quarter so that the reporting makes as much sense as possible.
If anyone has an idea of an elegant solution to this, I would be eager to hear it.
Thank you for your consideration!
- David in Tucson - QuickBaseCoachD7 years agoQrew CaptainI'm with Matthew here. You can create Roles and users in restricted Roles will not even know that the other Team Exists. Or give up on ever having Consolidated reporting. And also, if you split the app, every time someone has a bright idea to improve the app, you have double work to maintain two apps.
- DavidLichty7 years agoQrew TraineeHi Mark, Good to hear from you.
I agree, that would be nice.
This is a dictated business request. Imgine that these former teammates are going to be working for different companies and won't have access to the same data any longer.
The specific data for the work each team does will stay with them.
The link method I'm trying to preserve is to the table that lists all the team members, their managers, their desk-location, phone number etc. This person specific data is being split.
Since the date of the work they did is associated with them I'd like to maintain that association while splitting out the actual people across two completely different teams.
The key between the relationship is their Quick Base User ID, so that will remain the same.
When I make a new relationship to the new (split off) team's worker app/table, I end up with Related-team-member-1 and Related-team-member-2.
(1 links to the original app/table, 2 links to the new, split-off app/table).
As I'm spelling it out in more detail it is clear that it just can't work. I'll go for the wait until the end of a reporting period approach.
Thanks to you and Matthew for helping me process this!
Thanks,
David