Three Level - Expandable and Variable List Set (Is it possible?)

Question

Everything below is based on whether or not the concept is possible.

I am trying to design a SharePoint template for an Audit Structure that allows for the Control Codes to be placed in the Top Level, Entity being Audited in the next, and the Requirements in the last set.  I have included an image to better show the intent. 

I have only a general knowledge of SharePoint; due to time and need I am trying to figure this out on my own.  I have site Designer Access level and we are running SP 2007.  I do not have access to the Full Designer Software; this might be a a roadblock to me completing the task on my own.  However, if there is a way to do it, I still want to know how.  I can take it to our SharePoint admins and have them do it.  It will go faster if they don't have to figure it out too and I can just show them.

Description of site design.

Template, blank and variable.  I need to be able to add new Control Codes as needed and also Unique Questions and Entities underneath them as needed.  I know what fields I would need to add to the list items, but not how to get them to relate and create new and unique sub-entries.  In essence the Requirements will very likely be the same under each Control Code and Entities will be added and archived, but the Requirements may need different documents attached for each entity, so the Requirements will need to perhaps state the same requirement, but allow for documents to be attached and not shared through all entities.  One last thing, if possible, this should act like the dual level sort currently available, but in three levels  - [+] in from of Control Code and Entities, but not Requirements.  I am assuming all of this requires back end workflow, which I do not have access too.

- Any ideas would be welcome - and yes I know this is complex.

Answer 1

Hi,

This is a complex request.  You’ll need to create content types and several lists for this.  After that then you’ll have to do something links them together. Perhaps a master list(primary master object) that contains lookups to the smaller lists(audited entity).  The link part is going to be the difficult part because, once a user hits new item, a workflow (audited entity) does not fire until the item has been submitted.  So a user would have to first create the master item, save it, wait for the workflow to complete, come back and edit the item again after some fields have populated.  So this already is outside of your design requirements.

  
I think it might be best if you opened a ticket to talk to an engineer directly to discuss these requirements.  You will most likely need access to SharePoint Designer or Visual Studio for the workflow piece.

---

Regards, Savoeurn Va Microsoft Online Community Support