• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "MS Powerapps database"

Collapse

  • WTFH
    replied
    Originally posted by thelastrosbif View Post
    As you prefer, though practically everything released via M365 these days seems to be a semi-permanent beta test!

    For WTFH though this is about as simple an answer as he can ask for

    guess that's his call
    I've lobbed it over the fence to the guys behind the app and await their response.

    Leave a comment:


  • eek
    replied
    Originally posted by Lance View Post

    they do that with GA as well

    MS Store for business gone in January
    Different reason there - it’s hardly used

    Leave a comment:


  • Lance
    replied
    Originally posted by eek View Post
    When dataflows aren’t in preview and actually have an application lifecycle I might recommend them

    Until then MS could remove access at any point with a shoulder shrug
    they do that with GA as well

    MS Store for business gone in January

    Leave a comment:


  • thelastrosbif
    replied
    As you prefer, though practically everything released via M365 these days seems to be a semi-permanent beta test!

    For WTFH though this is about as simple an answer as he can ask for

    guess that's his call

    Leave a comment:


  • eek
    replied
    When dataflows aren’t in preview and actually have an application lifecycle I might recommend them

    Until then MS could remove access at any point with a shoulder shrug

    Leave a comment:


  • thelastrosbif
    replied
    Originally posted by eek View Post

    So how do you get the data from the CSV files into the Dataverse for Teams database? Remember API calls are not allowed because Dataverse for Teams is designed to be self-contained.

    Which is why I ruled Dataverse for Teams out in one of my early replies.

    Basically, outside of a Sharepoint list there is no way WTFH can avoid the $5 cost of a Power App per user per App licence cost. Because all the plausible escape routes were disabled years ago. And the reason Sharepoint isn't an option isn't because of slowness within sharepoint of the nightly data migration.

    One fix regarding that nightly run. Could you have a routine that identifies which CSV records have been changed relative to the previous run so only changes are sent to sharepoint?
    "Dataflows" are a specific integrated tool in Dataverse and Dataverse for teams, and do not count as an API Call in the sense you use it.

    You point the dataflow function at the data source almost exactly the same way as you would with Power BI, in fact it will let you do some basic data transformation in a power query window as part of this process too. As long as the CSV in a simple MS integrated location (OneDrive preferably) it syncs just fine. You could then set auto-refresh using Power automate flows.

    Announcing Power Query dataflows for Dataverse in Teams (Preview). | Microsoft Power Apps

    Just built and ran a test in my own tenant, a teams powerapp, a DfT table, a dataflow linked to a CSV in my OneDrive, and a refresh flow scheduled daily. Voila, works like a charm
    Last edited by thelastrosbif; 2 November 2022, 00:35.

    Leave a comment:


  • eek
    replied
    Originally posted by thelastrosbif View Post
    Unfortunately, we're talking about a database for power apps, not Teams. According to your link:



    Yes, and thats why you use PowerApps for Teams!

    It's the same as PowerApp, but you have to run it from the Teams Window. It's a dumb limitation but it is what it is. It is just as powerful and customisable as a regular powerapp + more, but you just have to get used to running it via Teams. If it saves you $2000 a month though, that's up to you. You can pop-out the Window and make it more full-screen-app-like, and also get access to Fluent UI components which regular canvas apps currently don't.
    So how do you get the data from the CSV files into the Dataverse for Teams database? Remember API calls are not allowed because Dataverse for Teams is designed to be self-contained.

    Which is why I ruled Dataverse for Teams out in one of my early replies.

    Basically, outside of a Sharepoint list there is no way WTFH can avoid the $5 cost of a Power App per user per App licence cost. Because all the plausible escape routes were disabled years ago. And the reason Sharepoint isn't an option isn't because of slowness within sharepoint of the nightly data migration.

    One fix regarding that nightly run. Could you have a routine that identifies which CSV records have been changed relative to the previous run so only changes are sent to sharepoint?
    Last edited by eek; 1 November 2022, 20:26.

    Leave a comment:


  • thelastrosbif
    replied
    [QUOTE=WTFH;n4239732]

    Unfortunately, we're talking about a database for power apps, not Teams. According to your link:

    • For any standalone Power Apps or Power Automate usage, which includes Dataverse API access as well, the Dataverse for Teams environment will need to be upgraded to Dataverse.
    [/quote
    Yes, and thats why you use PowerApps for Teams!

    It's the same as PowerApp, but you have to run it from the Teams Window. It's a dumb limitation but it is what it is. It is just as powerful and customisable as a regular powerapp + more, but you just have to get used to running it via Teams. If it saves you $2000 a month though, that's up to you. You can pop-out the Window and make it more full-screen-app-like, and also get access to Fluent UI components which regular canvas apps currently don't.

    Leave a comment:


  • WTFH
    replied
    Originally posted by thelastrosbif View Post
    Originally posted by Lance View Post

    Nope. Dataverse for teams is a separate teams-based instance of dataverse that incurs zero costs as long as you remain within the limitations given.
    The limits are something like:

    1 million records
    or 2 GB (ish) of storage

    Not huge, but for a single records-based app loading csv data its more than adequate.

    About the Microsoft Dataverse for Teams environment - Power Platform | Microsoft Learn
    Unfortunately, we're talking about a database for power apps, not Teams. According to your link:

    • For any standalone Power Apps or Power Automate usage, which includes Dataverse API access as well, the Dataverse for Teams environment will need to be upgraded to Dataverse.

    Leave a comment:


  • thelastrosbif
    replied
    [QUOTE=Lance;n4239724]

    Nope. Dataverse for teams is a separate teams-based instance of dataverse that incurs zero costs as long as you remain within the limitations given.

    The limits are something like:

    1 million records
    or 2 GB (ish) of storage

    Not huge, but for a single records-based app loading csv data its more than adequate.

    About the Microsoft Dataverse for Teams environment - Power Platform | Microsoft Learn
    Last edited by thelastrosbif; 1 November 2022, 12:44.

    Leave a comment:


  • Lance
    replied
    Originally posted by thelastrosbif View Post
    Dataverse for Teams with a dataflow that syncs to your CSV Location, preferably Sharepoint Online or OneDrive. That's all built in and costs nothing.
    isn't Dataverse for teams just a PowerApps DB in the background? So same costs? IE. The Teams bit is free but as soon as you fire up a PowerApps environment to run dataverse you have to pay

    Leave a comment:


  • Lance
    replied
    Originally posted by eek View Post

    And where is the record that needs to be updated coming from (remember sharepoint doesn’t work)
    I thought the performance issue with Sharepoint was for the backend not the user input.

    Leave a comment:


  • thelastrosbif
    replied
    Dataverse for Teams with a dataflow that syncs to your CSV Location, preferably Sharepoint Online or OneDrive. That's all built in and costs nothing.

    Leave a comment:


  • eek
    replied
    Originally posted by Lance View Post

    use Sharepoint for user input, and a logic app to scrape data from that into a blob store??
    And where is the record that needs to be updated coming from (remember sharepoint doesn’t work)

    Leave a comment:


  • Lance
    replied
    Originally posted by eek View Post

    WTFH needs users to update the records and that would require a premium license unless you use something within office (I.e. the sharepoint list that is both slow and crap)

    yes as a database it’s expensive but as a rapid development tool you can’t beat it
    use Sharepoint for user input, and a logic app to scrape data from that into a blob store??

    Leave a comment:

Working...
X