If you pass the ThisItem through to another screen you will not get all the data. This is because ThisItem will only pass the data that you show at the previous screen.
I believe that the ThisItem should contain all the data because that is more logical. If this behaviour is not desired then at least make it clear or make it toggle able.
I tested this with SQL Server and with the Entity System. This took me an day to figure out, so for me it wasn't clear.
Hi @Anonymous ,
You can store ThisItem in a Variable
and make it available on other screens - is this what you are asking?
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
It is not what I am asking. The problem is that Powerapps optimizes by only providing items in the ThisItem that are being used on the screen. Meaning that when you pass it on in the Navigate() function you can't access all the fields, only the ones you are displaying on the previous screen. Compare it to a traditional language like C#, passing a Class with all the variables in it. And that you want to see everything inside of that Class.
Hi @Anonymous ,
Gallery.Selected.xxx is also always available for any fields in the current record, which is effectively a collection of all the fields in that record. Anyway, I agree coming from VBA that there are many things you have to do very differently in Power Apps.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.