Great video, very useful and well explained! Maybe you have already fixed this in newer videos, but I do just to give feedback on that I do think the background music in this is a bit too loud. I like it having music, but right now I think it steals focus a bit too much :)
Hi Dork :) When you remove the environment variable prior to export - so that you can update it upon import - is this still considered a managed export?
What's up dork 😆 It's possible I'm misunderstanding the question, so let me know if this doesn't answer it. You'll leave the environment variable itself within the solution to include it in the export, but you'll empty the value. When you remove the value prior to exporting the solution, you'll be prompted to fill it in upon import. Your solution is still imported as managed without unmanaged layers. Mike has a couple videos that detail environment variables in more depth than I did - check out the "Pro Tip" section on his video Harnessing Environment Variables and he'll walk through what I've described above, I think this will help answer your question! ua-cam.com/video/uicLcGweeTk/v-deo.html&si=xLeoQKVpcSqyZsaj
How do you share environment variables with other users? In my solution I created environment variables and the other users in my solution cannot see or edit them. I also cannot see or edit environment variables they have created.
This sounds like a permissions issue; environment variables are stored in a team / user owned table. If you have the appropriate permissions or security role in the environment, you should be able to fix this by adjusting users' roles or table permissions - check out this Microsoft article for details on how to resolve this: learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables#security Let us know if that helps!
It depends on licensing requirements for the database - if you are planning to use tables in Dataverse (the back end of the Power Platform), you will need a license to support this; Microsoft has documentation about it here (learn.microsoft.com/en-us/power-platform/admin/pricing-billing-skus). There are other options outside of the Power Platform (such as SQL) which may have additional costs associated to them. Mike has a few videos about the costs tied to Dataverse that you may find helpful. His first video discusses moving from SharePoint to Dataverse (ua-cam.com/video/L0MXGKOY00U/v-deo.html) and the second one focuses on Dataverse and Model Driven Apps (ua-cam.com/video/YTvVqMYUs3s/v-deo.html).
@bulbDigital is it possible to change the power automate flow plan to other user who are co owners. Because if all the flows are running in my account, i will reach my limits. So i would prefer to run it in my co owner plan. And also for maintenance purpose i would like to stay in that flow. I would like to thank you for this wonderful content, The above question is a bit large, but is there any possible solution 🙂
This is a really great question! It depends on the trigger for the flow. If this is a scheduled flow or it runs automatically ("when an item is created," etc.), it will likely run under the owner's account. If this is a flow that a user manually triggers (via a canvas app button, for example), then it'll likely run under the context of that user. But, even that depends - if it's a child flow set up to use a specific user's connections, it'll run under that account, even if another user triggers it. Since most of the answer is "it depends," which probably isn't helpful, it may be easier for us to help answer this on the next Office Hours we host! If you join via Teams, we can chat with you to understand more details about your situation and provide a more informed answer. You can also join on UA-cam, but we'll be limited to talking over the YT chat. You can register for February 5th's session here: www.bulb.digital/office-hours It would be great to see you there and get to the bottom of this for you! :)
@@BulbDigital What does it mean I can get pretty far with Maker. is there a rule like this is possible with maker, this not anymore? and thank you for your reply :)
Sorry for being unclear - you can import/export solutions with Maker as long as there aren't Dataverse entities (as far as we understand). As soon as you want to import/export Dataverse entities, you'll need System Customizer.
You can do this just like a normal import and it'll identify the solution you're looking to upgrade - in the unmanaged version, publish all customizations, then export the solution as managed and import it into the destination environment! It should look similar to what the video shows; the import pane will help guide you through any necessary customizations like new, empty environment variables.
What gets in your way when using Solutions?
If it's not me, it's my idiot users.
Great video, very useful and well explained! Maybe you have already fixed this in newer videos, but I do just to give feedback on that I do think the background music in this is a bit too loud. I like it having music, but right now I think it steals focus a bit too much :)
Thanks for the advice! We appreciate it 😊
Sweet. Must try this. Also what a happy presenter. Well explained.
We appreciate the kind words! Thanks!
Great video with a great presenter.
Glad you enjoyed it!
this is a great video on solutions, thank you for putting this together!
Glad it was helpful!
I have that Mx Ergo mouse too! Nice mouse but I always get odd looks in work haha. It's a conversation starter for sure.
Good eye! ☺️ Of the three MX series mice I have, the vertical is my favorite! Instant pain relief in my wrist as soon as I switched.
Neat explanation. Currently studying for my PL100/200s and this was a good supplement for the course I'm already taking.
Best of luck! Glad that the video could help!
Hi Dork :)
When you remove the environment variable prior to export - so that you can update it upon import - is this still considered a managed export?
What's up dork 😆 It's possible I'm misunderstanding the question, so let me know if this doesn't answer it.
You'll leave the environment variable itself within the solution to include it in the export, but you'll empty the value. When you remove the value prior to exporting the solution, you'll be prompted to fill it in upon import. Your solution is still imported as managed without unmanaged layers.
Mike has a couple videos that detail environment variables in more depth than I did - check out the "Pro Tip" section on his video Harnessing Environment Variables and he'll walk through what I've described above, I think this will help answer your question! ua-cam.com/video/uicLcGweeTk/v-deo.html&si=xLeoQKVpcSqyZsaj
How do you share environment variables with other users? In my solution I created environment variables and the other users in my solution cannot see or edit them. I also cannot see or edit environment variables they have created.
This sounds like a permissions issue; environment variables are stored in a team / user owned table. If you have the appropriate permissions or security role in the environment, you should be able to fix this by adjusting users' roles or table permissions - check out this Microsoft article for details on how to resolve this: learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables#security
Let us know if that helps!
If i create a database needed for the solution, does it have a cost?
It depends on licensing requirements for the database - if you are planning to use tables in Dataverse (the back end of the Power Platform), you will need a license to support this; Microsoft has documentation about it here (learn.microsoft.com/en-us/power-platform/admin/pricing-billing-skus).
There are other options outside of the Power Platform (such as SQL) which may have additional costs associated to them.
Mike has a few videos about the costs tied to Dataverse that you may find helpful. His first video discusses moving from SharePoint to Dataverse (ua-cam.com/video/L0MXGKOY00U/v-deo.html) and the second one focuses on Dataverse and Model Driven Apps (ua-cam.com/video/YTvVqMYUs3s/v-deo.html).
@bulbDigital is it possible to change the power automate flow plan to other user who are co owners. Because if all the flows are running in my account, i will reach my limits. So i would prefer to run it in my co owner plan. And also for maintenance purpose i would like to stay in that flow.
I would like to thank you for this wonderful content, The above question is a bit large, but is there any possible solution 🙂
This is a really great question! It depends on the trigger for the flow. If this is a scheduled flow or it runs automatically ("when an item is created," etc.), it will likely run under the owner's account. If this is a flow that a user manually triggers (via a canvas app button, for example), then it'll likely run under the context of that user. But, even that depends - if it's a child flow set up to use a specific user's connections, it'll run under that account, even if another user triggers it.
Since most of the answer is "it depends," which probably isn't helpful, it may be easier for us to help answer this on the next Office Hours we host! If you join via Teams, we can chat with you to understand more details about your situation and provide a more informed answer. You can also join on UA-cam, but we'll be limited to talking over the YT chat.
You can register for February 5th's session here: www.bulb.digital/office-hours
It would be great to see you there and get to the bottom of this for you! :)
What security role do I need to export/ important my solution? Environment Maker or System Customizer?
Hey Laura, if you're making Dataverse changes, you'll need System Customizer, though you can get pretty far with Maker otherwise.
@@BulbDigital What does it mean I can get pretty far with Maker. is there a rule like this is possible with maker, this not anymore? and thank you for your reply :)
Sorry for being unclear - you can import/export solutions with Maker as long as there aren't Dataverse entities (as far as we understand). As soon as you want to import/export Dataverse entities, you'll need System Customizer.
Nice explanation. Thank you. How do you update / patch / upgrade a managed solution after making changes in the unmanaged solution?
You can do this just like a normal import and it'll identify the solution you're looking to upgrade - in the unmanaged version, publish all customizations, then export the solution as managed and import it into the destination environment! It should look similar to what the video shows; the import pane will help guide you through any necessary customizations like new, empty environment variables.