You’re offline. This is a read only version of the page.
We are building a model-driven app for a client who has many customers which will use the app to input data.
The client would like to have one big dataverse table and then different views visible for different customers to import data.
We have planned to do the import phase so that the clients customers using the app would use different excel template (based on their views) to import the data.
The client would like to have the data validated in dataverse, but I am not sure whether for examples business rules can be created for this purpose since the data is imported from an excel (not through a form). I recall reading from somewhere that business rules are not dataverse table specific and can not validate the data in a dataverse table? I was thinking that the data import needs to fail (and preferable show why it failed in the 'Import from excel' menu) if the data in the source excel does not correspond with the business rules assigned to the dataverse table, but I'm not sure if this is possible?
Thank you. The problem is that I am not using this app but the end users will be using it, and they are not very technical, so the app should be as easy to use as possible, hence the excel import through templates. But I realized that if you make a template based on a view, the template then has the dataverse column types also in excel format, so I think this will be fine for now. But I think dataflows will come in handy later because the client has requested us, if its possible, to make one big dataverse table based on the 10-15 smaller ones, which the customers will input data to via excel.
Hello, @Anonymous, using the OOB import data from Excel won't work for validation in your use case. Use the Dataflows to do the ETL. In the dataflows, you can utilize the PowerQuery to filter invalid data elements based on your customized logic.
If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.
Visit my Blog: www.powerplatformplace.com
Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos
Also, I found out through another thread that it's not possible to make views the way we had though and restrict access to them by users (https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-restrict-a-view-in-a-Model-Driven-App-to-a-specific/td-p/1698608), so I think we have to skip this one big dataverse table approach and simply make multiple tables with their own views.
#1
stampcoin
17
#2
mmbr1606
15
Super User 2025 Season 1
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
