You’re offline. This is a read only version of the page.
86
Hi all. I've seen questions relating to this but not quite exactly the same as I'm looking for.
I realise there are no enforcements in terms of what to name tables, but was wondering what other peoples approaches are.
Lets say we have a development environment where multiple apps are being created. These model driven apps are called App1, App2 and App3 (obviously wouldn't be in real life but for the sake of this question).
If a table is specific to one app and not used by any others, do you prefix (or any other description) the table with the name of the app it is used by, so you know it relates to that app? E.g. App1_Vacancy. Or do you just call it Vacancy? A problem with adding the prefix, is that it displays the name of the table on a form, so it looks messy if you've added a prefix (it would show App1_Vacancy rather the just Vacancy on screen).
My feeling is that if we do the latter (plain name) it might get confusing as time goes on as to what it used by what.
Furthermore, what if two apps need a table that is very similar but with some differences? For example, if two apps need a People table, but some of the fields/columns will be different, do you create a different table in each solution such as App1_People and App2_People to differentiate?
There is also the whole publisher aspect as well, so do people create a new publisher for each app instead?
If two apps need a People table but some of the fields/columns will be different, the apps can show different forms and views to tailor the user experience based on the nature of the app. The more important question is are those two apps going to share the same data? E.g. if the user creates "Person 1" in App1, should the user who uses App2 see that record?
Usually, the Dataverse environment is shared for the apps which have some common data.
If there are totally two different apps (e.g. Resource Booking app and Vaccination Record app) which do not share any common data, it would be better to have a different Dataverse environment for each app.
We usually use the same publisher for all the apps that we create. There are different publishers in one environment only when multiple vendors are working on the same environment for different modules with different managed solutions.
In my point of view table names should be descriptive to their functions or the data they're holding and not dependent on the app it is using so to follow your example it would be vacancy
For the people table still it is better to be one table and each app can have different forms to represent them data.
Publisher can be different per app but I don't believe it would be of any benefit.
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
19
#3
Michael E. Gernaey
15
Super User 2025 Season 1
Share
Report
All responses (
Answers (
