Skip to main content
Question

Import master detail record and assigning predecessors

  • May 7, 2018
  • 0 replies
  • 31 views

So I have the following main tables set up:

customers -< programmes -< projects -< sites -< tasks

I've created two import master detail records to import tasks from a template record to an active record for project and site tables and will most likely end up with something like:

programmes: 1 template
projects: 1 template
sites: x templates (to support standard tasks per service lines, ie. standardised deliveries)

The import master detail works well but I would like to know if it's possible to assign predecessors across a set of project tasks and a set of site tasks.  For example;

- imported project tasks could be (p1) start, (p2) deliver, (p3) close
- imported site tasks could be (s1) order, (s2) deliver, (s3) install, (s4) test, (s5) complete

During the import of the site tasks to a specific site is it possible always assign a predecessor tasks in the associated project?  In the example above, s1 should always have a predecessor of p2 (and if possible p3 should have a predecessor of s5).  This way the delivery section of the project is built from the sum of the site tasks.

Any thoughts much appreciated!

This topic has been closed for replies.

  • ArchiveUser
  • Author
  • Registered
  • May 15, 2018
Just a nudge in case anyone has an idea
  • DanLadner1
  • Registered
  • May 15, 2018
Hmm. This would be a little work, but I think you could create a formula field on the Tasks table to return what the predecessor should be (via some combination of summary/lookup fields and logic), then use a webhook to set those values into an actual predecessor field.

So if s1 should always have a predecessor of p2, you could pull the RID# of the p2 Task down (from the Project to the Site), then know what the predecessor should be for s1. Make sense?

Not sure how this would work if a Project has multiple Sites, though...
  • ArchiveUser
  • Author
  • Registered
  • May 18, 2018
Dan, thanks for your response, appreciated.  I like the suggestion but yeah, for multiple sites I think I may be on the path to a headache here...I'll keep digging away but I think this may just be something that will have to be done manually (editing predecessor) or creating more options in the import master detail that incorporate the predecessors
Terms & ConditionsAccessibility statement