You’re offline. This is a read only version of the page.
44
Dear All, Good Morning from Italy (forgive my bad English)
i ask for a friend 😀
i would like to develop a mobile application with PowerApps for my sales team (4 people)
in front of me i have 2 path:
Sharepoint List (i have a "good" knowledge)
Dataverse database (no prior knowledge)
i have an Excel table that contain our customer contacts, and i have to decide if make sense to split in 3 parts
list/table 1 with the name of the SalesAgent (4 people)
list/table 2 with the name of the Companies (around 600 unique rows)
list/table 3 with the name of the Contacts inside the Companies (around 1.500 rows)
do you think that Sharepoint List is ok
or
i need to study a little bit more for implement 3 Dataverse tables ?
is correct to implement a lookup in the following manner ?
list/table Companies with a lookup to SalesAgente
list/table Contacts with a lookup to Companies
One big problem, Dataverse requires another level of subscription. I have access to our Dataverse, but it turns out I can't create my own tables and use them because our current subscription does not permit that... I learned this the hard way after trying to build a table and then test out an app. I couldn't understand why it wasn't working, but after hours of more research, I learned that our subscription doesn't accommodate what I was trying to do. I won't lie when I say this made me very upset. I wasted hours of my own time.
Hello @Mammifero
1.as compare to SharePoint CDS has richer documentation management & collaboration
features available to citizen developer.
2.also you can create relationship in CDS but not in SharePoint,
3.CDS provide function like sum, min, max.
Thank You!!
Dataverse for Teams is free of cost.
It supports larger, relational datasets than SharePoint List.
Teams has over 150m daily active uses – build apps.
User aware about Power Automate and Power Virtual Agent capabilities
you can share your Teams Power App to users outside your Team.
High document collaboration use cases
Small data volume i.e. less than 2000 records.
No item-level permissions are required
You don’t mind if users have access to the data through SharePoint.
No requirement for a normalized data model
No requirement for intelligent processing such as duplicate detection, predictions, analysis
You only need basic field types
A small number of lookups are required
Relational data = Dataverse/Dynamics 365 Sales, or SQL
Unstructured data = SharePoint
Also, think of future extension and expansion. Suspect you are after more of a CRM than SharePoint - Dataverse will give you Contacts and Accounts (Organisations) out of the box plus a lot more, Dynamics 365 for Sales will give you a whole lot more from a sales point of view.
As per Eric I am a little bit biased as the CRM/Dynamics 365 is my background - but you need to use the tool that works best with the type of data that you will be handling.
Hi @Mammifero,
Although I might be slightly biased towards Dataverse, I would highly suggest to use Dataverse and is fairly simple to learn and get started. SharePoint is quite more limited, for example:
More info on Dataverse: https://powerusers.microsoft.com/t5/News-Announcements/Dataverse-is-not-a-database/ba-p/756215
Hope this helps!
#1
stampcoin
17
#2
ankit_singhal
11
Super User 2025 Season 1
#3
mmbr1606
9
Super User 2025 Season 1
Share
Report
All responses (
Answers (
