Background
I am using an MSForm to gather data from telephone interviews. I have used power-automate to take the data from each MSForm submission and put it in an excel spreadsheet.
The form is multi purpose using the standard branching functionality with MS Forms. The route through the form, and hence the data gathered, will vary depending role of the person completing the form and the circumstances they are recording. However each row will have some values that are common, such as the person making the call, the person being called and the date and time of the call. In that way there are never any empty rows or columns.
This all appears to work satisfactorily and I have produced pivot tables, charts and dashboards from the excel sheet. The simplicity of the solution is probably a good thing, partly because of my limited Excel experience and partly to keep maintenance reasonably low tech and simple. I do have a question though, which has been nagging at me.
Question
Is this the ‘right’ way to do this?
I am wondering whether a ‘cleaner’ and possibly more ‘technically correct’, solution would be to try to split out the data using a common ‘key’ field so that each flow through the MSForm would have data stored in a separate spreadsheet or workbook. From my very limited understanding of databases I believe that is how they work.
I would appreciate any thoughts on this - here are some questions I have in my mind:-
- Are there any significant down sides to the ‘one sheet’ solution that I have at the moment?
- Are there any significant benefits to the multi sheet solution?
- Are there any significant downsides to the multi sheet solution? I.e. complexity of creation/maintenance of pivot tables, dashboards, charts.
I haven’t created a dummy example file but would be happy to do so if my explanation isn’t clear.
Many thanks in anticipation.
Richard.
Hi Richard,
I would say that unless you're having performance issues with your data structured the way it currently is, or you're unable to perform calculations you require, then I wouldn't change anything as it sounds like your data is already in a tabular layout.
Databases structure the data in a relational format using multiple tables because this is an efficient way to compress data, enabling smaller file sizes and more agile models. They do this because they store a lot of data. So, like I said, if you're not having performance issues, then I wouldn't change anything.
Mynda
Thanks Mynda, that’s very helpful. My data is in tabular layout as you surmised and we don’t have any performance issue at the moment. I’ll focus on other areas.
All the best,
Richard.