Hello FLMike (as an aside, is there a way to directly reply to your comment?)
I've tried that but a ran into a few issues.
So I downloaded the data import template and that gave me a beautiful Excel spreadsheet. With 5 fields Pet Name, Owner, Species, Breed & Appointment Date. It even had a dropdown for the species so I could only choose the 2 species which exist as choices, Cat or Dog. I added one row to the .xlsx, saved, closed it, went to import. Got an error The file could not be uploaded for Pet: [UnknownError] Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=Excel file with more than one sheet is currently not supported.I did some checking but I'm 99% sure this data import template gives me a .xlsx with a single sheet called Pet. So I copied and pasted the data, into a new spreadsheet and uploaded that. I did the column mappings. Noticeably, I wasn't able to map the Owner field in the .xlsx to the Owner field in DataVerse (the reason why I have an Owner field in the .xlsx is because the data import template gave me one so I figured Microsoft know what they're doing, surely it's needed). Anyhow, I press import, and the same thing happens Type=Microsoft.Dynamics.Integrator.Exceptions.IntegratorClientException, Msg=Unable to parse import file 5d385509b2584ec78afa0bc835d22403.xlsx Error details PQOnline failure - Type=System.Net.WebException, Msg=The remote server returned an error: (400) Bad Request.
The 18 other fields, are all fields that were generated for me when I created a table in DataVerse, they are for completeness Created By, Created By (Delegate), Created On, Import Sequence Number, Modified By, Modified By (Delegate), Modified On, Owner, Owning Business Unit, Owning Team, Owning User, Pet, Record Created On, Status, Status Reason, Time Zone Rule Version Number, UTC Conversion Time Zone Code and Version Number.
Of these the following fields are required, they all get autopopulated when I just type into the table, so I would expect a high quality product from Microsoft to continue to autopopulate these fields if the data is coming from an Excel spreadsheet as well surely. Owner (this is nothing related to who owns the object I'm modelling, rather it's the built in field, I imagine it's the owner of the data record, possibly for some row-level validation security, if I ever get that far on my Power App journey); Owning Business Unit, Pet (A GUID which serves as the PK for the table if I'm not mistaken), Status (which just seems to be active for all the pets, I imagine this built-in field will be useful one day if I ever want to do soft deletes from my table).
Thanks for your help so far FLMike
P.S. I still feel like I'm missing something. Isn't Power Platform supposed to lower the bar to be a software developer, through intutive low-code solutions? With these error messages which seem to be (a) false, or (b) incredibly uninformative, and templates being generated by supported Microsoft tools that don't work out of the box, it feels like I'm working with legacy technologies all over again xD
