
Announcements
Good morning,
I'm working on developing a quality assurance app related to interactions with our members, and other audits. Because of the number of criteria we have (upwards of 120 at the moment, with a further review likely to have more) and the requirement to have 'blank' columns to allow room for new criteria to be added, multiple SharePoint lists will be used.
Because of this, the columns with identifying data for the review (e.g. consultant, reviewing agent, time and date of call etc) will be the same across all lists so I essentially need to take the input from one datacard and save it to multiple lists.
I also need to be able to record data from the one form spread across multiple lists depending on where the criteria is housed. For example, correct identification criteria may be on list 1, while accurate communication criteria may be in list 3 but will need to be input from the one form for one interaction.
I've only worked with one list before, and haven't really investigated or made use of collections, but I'm wondering if they are something that would assist here, or if anyone has suggestions on where I should start?
@Farsie Instead of making your tables wide (lots of columns) make them tall (lots of rows) by designing relational (parent-child) database. Here is video by Daniel Christian that will help you understand the concept. The concept you are using is not the best method, because you will end up lots of duplicate data and that can lead to data integrity issues if the repeating data (consultant, reviewing agent, time and date) for a given record don't match in all different lists.