4 Replies Latest reply on Jul 16, 2014 1:45 PM by philmodjunk

    Populating tasks with information

    abunce515

      Title

      Populating tasks with information

      Post

           Hello - and as always, thanks in advance for the help.

           This currently works on four tables - Listings, jn_TaskType_Listings, Task Type, and Tasks

           I am putting this information on the listings layout.

           What I am doing is using a portal from jn_TaskType_Listings to select something like "buyer" or "seller".  After selecting that I have another portal from the Tasks table that shows all the tasks with that particular TaskType.  

           This is working successfully.  But what I am wanting to do is add fields that I can input the task completion date.  and the task due date.  And I am assuming I can't put these fields in the Task table because then the field contents would reflect on all the separate listings.  I can't put it in the Join table because then that would just give me info for the complete set of tasks. 

           With the due date I am wanting to do a calculation field that takes the days field (will be a number) and adds it to the listing date if its a seller, or the acceptance date if its a buyer.  

           any help is appreciated, thank you.  

      Untitled.jpg

        • 1. Re: Populating tasks with information
          philmodjunk

               Your conclusions are correct. The current data model does not support what you want to do.

               When I looked over the data model first before reading your posted text, the question that immediately popped into my mind was "why is TaskType the parent of the join table and not Tasks? And then reading your post simply confirmed that I has spotted the issue.

               I don't know that you need a table of task types at all. This would seem easily replaced by a simple custom values value table. But if you do need to store the values in a table, it would not seem to be something to set up like you have here as a related table.

               I think that you have two different goals to accomplish here. The first would seem to be the need to assign a "task type" to a specific contact linked to this listing. I can't quite see why a "listing" would be labeled as  "buyer" or a "seller" (these are properties listed for sale aren't they?) as would happen in the current set up. I think that you have a contacts table that should also be linked to listings with a join table where you specify the task type in order to accomplish this first goal.

               The second is to link specific tasks to this listing in such manner that you have a place to record information specific to  the "link" between listing and task.

               Listings-----<jn_Tasks_Listing>-------Tasks

               In this set up, the join table record links a single record in tasks to a single record in Listings and then you can add any due dates and completion dates needed as fields in this join table.

          • 2. Re: Populating tasks with information
            abunce515

                 Phil - once again you have proven to be my hero.  

            • 3. Re: Populating tasks with information
              abunce515

                   looking at this i think i am still stuck.  

                   The tasks are associated with the listing, so I really want to keep them with the listing and not the contact... contacts will have their own tasks of a different category, such as get pre approval letter, and follow up phone calls. 

                   But delivering an abstract, placing a sign in a yard, taking photographs, publishing to the web, these are all listing related tasks.  is there a way i can keep them that way and still meet my goals?

              • 4. Re: Populating tasks with information
                philmodjunk

                     What I described allows you to do exactly that. If you don't need to link tasks to contacts (which is what your original post suggested with references to "buyer" and "seller"), then don't do that part of the change. The details that I spelled out specifically are only the part that links a listing record to a task and the join table then becomes the place to add your due and completed date fields.