TeamDesk Knowledge Base & Support

cooper collier  1/10/2014 3:56:06 PM

Have you set a user property table. This allows you to define more columns/fields for a users, then you can effectively make groups and link the groups to the other tables.

I am doing something similar with the database I have created.
I call it teams,, and it links to staff
and once you do this you can do all sorts of organizing. Including notification emails.

here is a sample of my table
https://www.dropbox.com/s/lt5xaurqh5ifu3y/teams.jpg

and here is what the staff looks like, this is the user properties
https://www.dropbox.com/s/fset4u4fw6baxzu/staff.jpg

if you need help or want to see how I did this let me know.
I can find time to show you.

basenine 1/11/2014 12:36:18 AM

I Agree with above...

I'm currently writing a DB for a school which can effectively be used by, say, the Education department of the World(!). Each Staff Teacher user can only see their School (out of a list of 1000's) and then only see their current students (and their Student's related information - role calls, parents/guardians).
A School Administrator/Principal user can see their School and all of their Staff-->Students--->Parents etc.
The Education department can see the whole lot.

The only way to achieve this is with the user properties table and relating that table to the other appropriate tables.

Beware that it might 'do your head in' as some of the relationships can be complicated ---> Multi referenced teachers for students that attend more than one class--->Multi referenced Parents (if you're doing an Emergency contact list for your students)...it takes time but it is possible.

Good luck 😀
Brett

basenine 1/11/2014 12:45:21 AM

The above and Mutli Relation views will also work...relations and references are different

Luison Lassala 1/16/2014 4:58:15 PM

Thank you for the comments and suggestion: I must investigate the User Properties Table - but it's not the solution for the problem I was looking for: replicating detail data for a master record every month.

Mila Shvets from TD support provided me with a very neat solution using a Multi-Record Table View Button. Thanks Mila!

basenine 1/16/2014 5:02:32 PM

Great to hear... When I re-read your post, I realised that a multi relation view would work better...hence my addition.

TD Support is always fantastic at pinpointing solutions quickly and easily.

Good luck with the rest of the build 😉

Mila Shvets  Staff  1/17/2014 5:26:30 AM

To replicate detail data for a master record via Multi-Record Table View Button, please make the following adjustment:

At first create a new reference column (Many-To-One type) in the Details table referring to the Master table. Let’s name it “Complementary reference column”.
Then create a Multi-Record Table View Button. This button will edit the “Complementary reference column” and will be placed in the details view you want to replicate.
When the button is created, you can add the New Record Create action with Assignments.

Don't forget to add the assignment where the “Complementary reference column” data is copied to the reference column used in the relation.

The “Complementary reference column” can be removed from the form and excluded from the default view, because it is needed only for the button.

How the button works:
You select all details records you want to replicate for another master record, click on the multi-record button and select the master record in the “Complementary reference column”.
As the result the system replicates details for the chosen master record.

How to create a reference column you may read here http://www.teamdesk.net/help/4.3.aspx
You may read more about Multi-Record Table View Button here http://www.teamdesk.net/help/11.1.3.aspx
about New Record Create action here http://www.teamdesk.net/help/11.4.3.aspx

Regards,
Mila