3 Replies Latest reply on Mar 20, 2010 2:00 PM by comment_1

    Better solution to tagging one and only one post in a portal?

    paint

      Title

      Better solution to tagging one and only one post in a portal?

      Post

      I have the following tables in my project which comment helped me with earlier

      Relationships through ID but still see informative text

       

       

      • Projects
      • Team
      • ProjectTeam (connecting Projects table with team table via foreign key ID#)

       

       I can choose the Project team members for each project via a dwindling list (thank you comment @ FM Forums for the example file)

       

      I now would like to tag a project manager for each project (but only one per project)

      I have solved this by adding following fields in the ProjectTeam table

       

      •  “ProjectManager” field with a checkbox of only one value (1)
      •  “ProjectManagerChecking” field with Auto-Entered, calculated value and validation for a Unique value.

       

       

      Case(

          ProjectManager=1;

          ”X1T”& Team::TeamID;

          “XT” &  Team::TeamID & “P” & Projects:: ProjectsID

                 )

       

      If the team member is added but not tagged as a project leader he will get a number unique for team and project in the ProjectTeam table (XT015P132).

      If the member IS tagged as a project leader he will get a number only unique for each project (X1T015).

      If another team member is tagged the validation process will take command and tell me to “Revert Record”.

       

      Is there a way to solve this in a “cleaner” or perhaps more professional way? Perhaps without having to press “Revert” twice when I do something wrong.

      I could just set a projectmanager-field in the project table and get the information from the Team table but then I would have the unwanted possibility to select the project manager in the project team also. Some will do it, some will not. 

      Without saying to much I really would like to give my colleagues a minimum of options to f*ckup.

      Anything besides “normal” behavior is considered bad (such as pop ups) but I know that in the long run people find their own “creative” ways of filling in and storing information.  

        • 1. Re: Better solution to tagging one and only one post in a portal?
          comment_1

          Since every project has one manager only, this is an attribute of a project and should be stored there. I didn't get this part:

           


          paint wrote:

          I could just set a projectmanager-field in the project table and get the information from the Team table but then I would have the unwanted possibility to select the project manager in the project team also. Some will do it, some will not.


           

           


          • 2. Re: Better solution to tagging one and only one post in a portal?
            paint

            In my Team table I have all the personnel at work. All of them can be project managers and project team members.

            I made a dwindling list of the lot to choose from as a project team.

             

            If I save the project manager in a field within the project table, this name will still be visible in the dwindling list as a possible team member.

            The user initiating a project then has the possibility to include the project manager within the project team or not include him (forget).

             

            At our workplace we tend to change project managers from time to time depending on workload. The previous project manager then takes place as a regular team member.

            If the project manager is not chosen as a team member he will not be included in the group automatically when he steps down.

             

            This is one reason. The other would be that I in the future would like to exclude and include projects depending on the user.

            User A would only see projects of which he is manager of as a start screen and be able to choose all projects of which he is a member(and manager) when he registers his time.

            In my imagination it would be easier for me if all of this information will be stored in one table.

             

            Although; empirical studies show that chances of me being wrong: 95% 

            • 3. Re: Better solution to tagging one and only one post in a portal?
              comment_1

              You are mixing structure with user-interface. Structurally, the identity of the manager is an attribute of a project. The user-interface issue can be solved by allowing project manager to be selected only from team members assigned to the project - by using a restricted value list, for example, or by selecting from the portal. The important thing is that selecting a manager this way automatically deselects the previous manager.