Unanswered

Powerapps vs VB.net

(0) Share

Report

Posted on by Cristina_Mizar

I need to develop a data entry application for budgeting purpose.

We have a DataWarehouse built in Sqlserver and the idea is to connect directly to sql. As my end users use power bi ( direct query to an ssas tabular model drom power bi) my first idea was to use powerapps, that would allow to embed the powerapps app in the same power bi report.

After playing a bit with powerapps I am wondering if it would be better to perform an vb.net app, so that the budget application will require of some not so simple functions.

I will appreciate your advice,

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

timl 36,383 Super User 2025 Season 2 on at

Like (1)

Report

Hi @Cristina_Mizar

Here are some initial thoughts. It might be helpful if you could advise if it's on-premise or SQL Azure that you're using. Also, what kind of 'not so simple' functions do you want to implement? If it's just simple data entry that you want, PowerApps can do the job well.

Pros/Cons of PowerApps
+ Can run on multiple devices such as mobiles/PCs
+ Users can run the app outside of your internal network
+ Deployment of the app is easy

- Subscription cost could be expensive - SQL Server (on-premise) uses a premium connector

Pros/Cons of VB.Net Forms
+ With VS community edition, free to use. No ongoing subscription.

Was this reply helpful? Yes No
Cristina_Mizar 21 on at

Like (0)

Report

Hi @timl, Thanks for your fast response.

I am using SQL on-premise. I have already done some tests with the premium connector, using procedures for modifying data in the DB. I have adquired a single subscription so far but,I imagine I'd need a not free subscription for any user that would use this app through PowerBI, right?

In essence, the application will be a HR budget for an Hotel Chain . It will be used by every hotel director and also by HR. The idea is to start from a list of employees based on the real staff of the selected month , with their real costs of that month (this info comes from the SQL DW) being able to modify their salaries and add or quit employees. Next step is to , for each month , assign to each employee a percentatge of ocupation. It can be also obtained from the DB or can be done from zero.

Was this reply helpful? Yes No
Verified answer

timl 36,383 Super User 2025 Season 2 on at

Like (0)

Report

Hi @Cristina_Mizar

Yes, every user that uses the app would need a license.

From your description, I think that building this logic in PowerApps would be no more difficult/or easy than doing it in VB. For anything data related that's too complex to accomplish in PowerApps, you can put the logic in a SQL Stored Procedure and call it with Flow.

Was this reply helpful? Yes No
Cristina_Mizar 21 on at

Like (0)

Report

Hi @timl,

Ok, I'm goint to try to develop it with Powerapps,

Thanks for your time and your advice,

Was this reply helpful? Yes No