Thank you. That's the first honest and helpful answer I think I've received out of any of my queries on this or other forums.
So is Dataverse--being a layer on top of SQL Server (which I assume is Azure SQL so I guess I'll need to get versed on the differences between it and SQL Server)--design more of an abstraction layer for making things easier for non-developers? If not then what's its purpose?
As for your question of why use Dataverse, my answer is that Dynamics Field Service depends on it as far as I know. As I researched FS I found that it had much of the functionality that we needed. As we got started with it and got further into the weeds I find that it seems like an half-baked app and coupled with the limitation that (I thought is blamed on Dataverse) of not being able to create forms with grandchildren records I'm starting to wonder if we made a bad decision going with Dynamics.
This specific issue is that FS doesn't seem to have a time log acceptance business flow--even though it seems to be marketed as having one.
I'm trying to create a tab on the Work Order that shows each Time Entry and it's notes as editable data and have a checkbox to accept the time log.
It turns out that for some reason Time Entry notes are not in the Time Entry table but rather in a Bookable Resource Booking Quick Note table, and worse that table doesn't have a relationship with the Time Entry. Therefore an admin can't look at a time entry and see the notes of what's done and the time it took and accept it nor change the amount of billable time we'll bill for that specific Time Entry.
Seems it's going to take a lot of customization to get there and wondering if it's worth it to go down that road and then continue to hit road blocks at every turn with FS365.