I agree 100%. I would create a SharePoint List to hold the values and allow the Admin of my app to manage those values within the app itself. I guess the same would go for lookup columns, those that look up values from other Lists. Keep it simple when storing the data to avoid delegation issues down the road. I did not know about the Dataverse Yes/No column being a choice. Thanks for the insight.
Hello, I love your videos! May I ask for some advice on how I can create locked tabs? when they finish the first portion, then it’ll unlock the next tab and so on and so forth! Looking forward to hearing from you, thanks!
To create a series of locked tabs in PowerApps where completing one portion unlocks the next tab, you can use a combination of variables and visibility properties. You can start by initializing the variable to toggle the tab visibility on the OnStart Function: Tab1 can always be true/visible Set(isTab2Complete, false); Set(isTab3Complete, false); Next:: If the form has been properly updated on the current tab, then update the variable status to show up/navigate to the next tab. If you need more info, join my FREE community 😊 🍦www.skool.com/power-apps-community
You do not need a PowerAutomate flow. Once the first section of the form is completed, when the next button is clicked, you set the variable state from false to true. 😊
Hi sir, I've been following your videos and I've learned alot from you. But I'm currently stuck on a project I've been working on. From Jos, Plateau State Nigeria. I have two list, both are SharePoint list, I want to be be able to create an item on the second list (taken an item from the first list and making it an item in the second list), On the click of a button. I've tried using patch function or using power automate, all to no avail. I've watched videos and read, did everything for days now and yet I'm still stuck. Can you please help me sir
Sure i can help! One way to do this is to save the record/items of the first list in a variable or collection, then perform a patch to the respective columns of your second list e.g. Patch(SecondList, Defaults(SecondList), { Column1: FirstListColleciton.Column1, Column2: FirstListColleciton.Column2....etc }) If you have further challeneges, join my free community here that is packed with an army of seasoned developers: www.skool.com/power-apps-community 😊
I disagree with this one :) (hopping to understand correctly all you said as english is not my language) Choice column (at least in dataverse) are responsible of getting the assurance that your datas are what you planned for. The first 2 solutions you give us are not a good option as : 1/ text can be changed easily by anithing else that is not intended in your app, 2/ collection in your app is only working within your app. Data modelisation is here to give the assurance that whatever your apps are (Canvas, model driven or whatever) your datas are consistent. If a new dev use your datas, he shouldn't have to learn all the dev specific tips to use it. Data modelisation should be enough by itself. That's why options are a good choice wherever your data model needs it. Your third solution may be better, but not the best : you have to reinvent the wheel to do exactly the same as a choice column does. It is only helpfull if your choices needs to handle some other datas with it, because a choice column can only handle a text (and a number). Finally the only thing I agree is for the boolean column... What a shame to not have a real boolean, instead of this brain f***g yes/no option
