Dear Alireza, I've been watching your videos for a couple of days. I have kind of experience with Power Automate and P Apps. Your content is very clear, straight to the point. Really nice!
I humbly say "Thank you" for your time and yet another wonderful session. You're the best @Alireza Aliabadi . Can't wait for your next sessions. Just to caution users trying to replicate on the fly. You need to make sure to close the parenthesis after ItemID like this -> LookUp(,ID=ItemID). If we miss and add this after the records, it will create new records in back-end instead of editing the current record. PS: Could it be possible to use modern controls instead of a legacy control? Most of these are changed and end users fancy using new UI and I understand the core still remains the same.
6 місяців тому
Could we use the As Operator instead of renaming columns in such scenario?
BTW, I've faced a challenge with gallery and patch. In a gallery, I need to refer the previous record of the current and didn't find any nice solution. I have 3 records (coming from SP List plus a toogle (yes/no). The toogle 2 must be available only if toogle 1 (first record) is "yes", and so one. Do you have any video which explain how to?
Dear Alireza, your Udemy courses have changed my professional life. Thank you for another excellent tutorial
Nice Use of Collections!
Dear Alireza, I've been watching your videos for a couple of days. I have kind of experience with Power Automate and P Apps. Your content is very clear, straight to the point. Really nice!
Thanks alireza
Beautiful
I humbly say "Thank you" for your time and yet another wonderful session. You're the best @Alireza Aliabadi . Can't wait for your next sessions. Just to caution users trying to replicate on the fly. You need to make sure to close the parenthesis after ItemID like this -> LookUp(,ID=ItemID). If we miss and add this after the records, it will create new records in back-end instead of editing the current record.
PS: Could it be possible to use modern controls instead of a legacy control? Most of these are changed and end users fancy using new UI and I understand the core still remains the same.
Could we use the As Operator instead of renaming columns in such scenario?
Absolutely. I personally would rather go with RenameColumns for better clarity in the code, but both ways work equally good.
BTW, I've faced a challenge with gallery and patch. In a gallery, I need to refer the previous record of the current and didn't find any nice solution. I have 3 records (coming from SP List plus a toogle (yes/no). The toogle 2 must be available only if toogle 1 (first record) is "yes", and so one. Do you have any video which explain how to?
This is easy. Remember that in PowerApps there is a function called "Index".
I leave the rest to you 😉