What I'm referring to when I say "push to [test, prod]" is overwriting (or updating / upgrading) the current version of the Solution you have in your Test Environment or Production Environment with a newer one. Think of when your phone says you have a new software update available, it's because they "pushed" a new update. Since we made this video, there are now more ways to do this; my favorite is with Managed Pipelines, but you can get by with manually exporting and importing a Solution. I have a video explaining the second process, I think you'll find it helpful: kzbin.info/www/bejne/oJW1aX5mp5x4hqssi=sLa9wvrmOcKRffNF Managed Pipelines are a newer feature in the Power Platform - they install a UI in your Solution that uses a single button to initiate a deployment. It automatically takes environment variables and their values into consideration and makes the process of ALM so much easier and straightforward. They do require some configuration and additional resources, and most folks likely will not have the permissions to set it up themselves. If you have a team that governs the Power Platform in your tenant, they would be a good place to ask about this. You can read more about it in Microsoft's documentation: learn.microsoft.com/en-us/power-platform/alm/pipelines Does that help answer your question? 😊

@@BulbDigital wow so helpful. Thank you. May I also ask if you have any videos on end to end power apps projects? ❤️

Glad it was helpful!

Glad it was helpful!

Power Pages licensing / pricing is in addition to M365 for business licenses and is also licensed differently than your standard M365 user licenses. Specifically, Power Pages is intended as a tool for engaging with external users. These would be your customers or maybe other partners, but are not licensed users in your tenant. To that end, the Power Pages license packs come in two flavors. Anonymous users, and Authenticated users. Anonymous pack licensing comes in packs of 500 anonymous users per site, per month and is $75 USD per month. Authenticated licensing packs come in quantities of 100 users per site, per month, and is $200. Here's a link to the current pricing... www.microsoft.com/en-us/power-platform/products/power-pages/pricing#:~:text=Explore%20tailored%20pricing%20and%20subscription%20plans?msockid=04019546c9446e75271086a8c8d76fef

Thanks Carlos. We don't generally recommend breaking inheritance because it creates so many new places to go to adjust permissions in one site and users can struggle to find and identify these over time. There can be exceptions to this rule if the site owner can and is willing to keep track of where permissions are different in a site, that's just easier said than done. In the case you mentioned, you can break inheritance on all of those folders and it will keep the existing groups that were given access. New people added to those default groups will get access but new groups added at the top-site level won't get access.... many people assume there's no broken inheritance and don't realize why top level permissions don't apply to those folders. Then you also have to manage people and groups on every one of those folders at the folder level. As an alternative I would consider migrating each project folder to it's own SharePoint site collection and add those project members to the root of the site. An organization that did that would have a standard that every project has a site, all permissions are managed at the root of every site collection, and they wouldn't have "hidden permissions" on multiple libraries or folders.

When using your F3 account in Power Apps, are you accessing a Power Apps environment that has Dataverse enabled / installed? If Dataverse is not enabled in that environment, there will be no tables. In order to use Dataverse you first need to provision a Dataverse enabled environment. You can do this from the Power Platform Admin Center, provided your account has the Power Platform Admin Role. Also wondering, are you trying to develop a Dataverse app using a front line worker persona? It seems like you would develop the app with a developer account (maybe your E5 license) and then you'd simply share that app with your F3 enabled account so they can use the app, in which case there's no need or expectation that they would be interacting with Dataverse tables directly.

@@BulbDigital I am the only user, the default environment has Dataverse enabled, but not managed, and my F3 account has the admin and app maker roles as well. I'll try moving the Power Apps Premium license to the E5 account.

Whoa now! We would not recommend modifying Dataverse in the Default environment. You only get one Default environment for your organization and this is where all of the "personal" automation takes place. Making changes here might adversely affect many of the out-of-the-box functionality as it pertains to M365 and dependencies on the Default environment. For example, all of the standard Approvals that you may run in Teams, or from SharePoint are all managed within the Default environment within built-in Dataverse tables. The good news is when you stand up a separate / dedicated Dataverse enabled environment, you get all of those baseline tables that you can build on top of.

@@BulbDigital thank you!

Hey @smailisamir9688. You can see the initial demo of the automation at the beginning of the video just after the intro section. You can see it working here: kzbin.info/www/bejne/kIuonGeJn82gnJI

Happy to help! Glad you found it useful, best of luck with everything - feel free to reach out if you need help!

We're still going strong! You can register for the next one here: www.bulb.digital/office-hours Or watch back previous ones here: kzbin.info/aero/PLNvxuwCIyGhFyG70J2_FUft5N1ng6_MrY

I know, right? Imagine if we had gone on for 12 minutes!

Ahh, there's that sunk cost biting again! I think there's a couple things I would say in response to this comment. First, if you're going the Dataverse route, your'e going to pay for some licenses. If this is the case, then maybe rebuilding your app as a Model Driven App rather than keeping your Canvas investment should be considered. I say this because I believe 90% of the time you can build the same functionality with a Model Driven App in less than one tenth of the effort. I have a new video we just released that lays this out in more detail. Second, the document problem has long been solved with the use of SharePoint Document Integration. Check it out... learn.microsoft.com/en-us/power-platform/admin/set-up-sharepoint-integration

Thanks for the feedback John

Thanks for the feedback John!

If we could wave a magic wand, we'd make it a lot less confusing. Until then, we're here to help you navigate the complexity 😊

Glad it was helpful!

We ❤️ our haters

Thanks for the feedback John!

Thanks for catching this! Yes, we use DevOps solely with Agile/Kanban boards so we use the term "DevOps board" interchangeably on our team but I can see how that could be confusing. Thanks for watching!

Thanks for catching that, just got them updated!

Fingers crossed for the future :)

Oh we have lots of thoughts about Planner :) kzbin.info/www/bejne/rJOTqJ14i5Wnes0

We actually just mentioned this comment to the Loop product team about how some of those things can cause red flags to get raised about the app's future. They were very quick to assure Loop is not going anywhere, and will be working on some ways to communicate to companies about their level of commitment.

v2.0 of Loop just launched this week.

Great to hear they're helpful! We'll keep them coming. It can get tricky fitting all of it in one video! We're considering doing webinars and such on the topic, would definitely encourage you to jump on our waitlist if that sounds interesting: forms.office.com/r/q7tevtN2rd

@@katasticone yesssssss!!!!! 100% agreed

We haven't, but that's a great idea! I know there's lots of systems like that that people use, it would be great to be able to see if/how it can. be done in the Microsoft world.

@@BulbDigital I am about to finish a working model. Maybe we can link up when it’s done…..

Glad to hear it's helpful Andrew!

We hear you! Checkout the webinar: viaworkplace.lemonsqueezy.com/checkout