Lookup in Default - Not working as expected

[Anonymous]

I ran into an issue whereby pulling the default value of a SharePoint List item via lookup works with Set (gloabl variable) but not with UpdateContext (local variable). 

Context: (This is all on one screen)

1. I obtain the item ID by clicking on a gallery item
   1. Method 1: UpdateContext
      UpdateContext({localID:ThisItem.ID})
   2. Method 2: Set
      Set(globalID,ThisItem.ID)
2. I set the default variable of any input item (textinput/dropdown/combobox) in this example textinput
   1. Default: LookUp(SharePoint_List, ID=localID, col1)     --> shows nothing
   2. Default: LookUp(SharePoint_List, ID=globalID, col1)   --> displays result

This 'bug' initially only occured on the published version, however, after turning off the 'Explicit Column Setting' this started occuring in preview mode also.

I can see the ID updating for both the localID and globalID via separate text labels and both show the same ID. Thus, I am confident that both are obtaining the ID from the gallery. However, it appears that the textinput (and other inputs) are not fetching the lookup value when using the localID via updatecontext.

I have tried recreating the inputs from scratch and I can't even get a consistent result?! The exact same code works sometimes and sometimes doesn't. I understand if the error/bug is consistent, but it behaves differently evertime... Please refer to the GIF attached which shows the Set method working and then... the updatecontext working for one  and not for the other.

I have not been able to consistetly recreate this issue unfortunately and can cofirm that this issue was not preset over the past few months that the app has been running. 

In the meantime, I will reassign all my inputs to have a default value based on a descriptive global variable,  however, there is clearly an issue here if developpers can't rely on the use of local variables which have their place. 

Any help would be appreciated, as this does not make any sense to me. Please refer to the attached GIF that demos the issue. 

[iAm_ManCat]

Hi,

In your example image, the code on your textinput is different to the described code in blue - you are stating that it should be using ID in the blue labels, but your formula bar says you are looking at GUID, and comparing it against selectedID, which is not localID and not globalID

[iAm_ManCat]

I tried recreating it, but I'm able to use both context and global variables even within a vertical container, and with the explicit column selection both off and on:

[Anonymous]

Hi @iAm_ManCat , 

Apologies fo the inconsistency. In the body of my description, I have used generic names such as 'SharePoint_List' and 'ID'. My actual list has its own name and the ID column is simply renamed to GUID in my list.

To confirm my actual lookup in the textinput is looking up against GUID. To avoid confusion, I have posted the equivalent code/image below as per my description. 

As dispalyed at the bottom, I can see the lookup working as expected on the bottom two, one of which (in blue) is identical to the textinput above (enclosed in red)

I have redacted any information relating to my actual list for privacy/confidentiality reasons. 

[Anonymous]

Thank you for attempting to recreate my issue. I have also tried recreating the issue without any luck, but have encountered this in the past and specifically in this scenario. 

My suspicion that it is a potential bug arises from the fact that I have identical textinputs demonstrating different behaviours. 

In my screenshot, you can see that when I click on the textinput enclosed in red, and I pull up the evaluated result of Default (by clicking on the end of the code) - it shows '75'. BUT on the default on the right it shows 'No Value'. 

So it appears that it is evaluating it within the code, but not propagating through as the result of default for some reason?

[Anonymous]

To add to the weirdness:

In the textinput that is not working. I have cut the 'selectedID' and pasted it back in its place (nothing else) - and the expected result magically appears. Please refer to the gif attached 

However, if I save this and publish - it does not appear in the published version. And it appears blank again if I reload the editor. 

As I mentioned, I can't replicate this issue and I imagine others may be able to replicate it consistently either. I have seen this happen before, but typically recreating the object from scratch has fixed the issue. Unfortunately, in this case it doesn't seem to consistently fix. 

[Anonymous]

Further Updates: 

Upon further investigation, I have found the issue to be consistent on this screen when using containers.

When I dont use a container and dispaly a text label, it will display the localID.

When I place the label inside a container (blue and orange are separate containers in the image) the lookup does not display. Further to this, not even the concatenated text placed in the the same label displays.

It's almost as if the app is treating the container as a separate screen. But even then, the concatenated text should show with the lookpvalue showing as blank. 

It's frustrating as the app functionality turns the container visibility on and off, with many components within the container. It's much easier to manage and cleaner to use containers. I have the same functionalty working on other screens and other apps, so I can only imagine that this is a bug.

Please refer to image below. 

[Anonymous · Accepted solution]

I ened up recreating the whole screen and it works fine now. Not sure what was happening. 

[iAm_ManCat]

This is going to sound a bit nuts, but could you try wrapping it Text( ) as its reading it as a number field

..also can I see what it is inside of - you mentioned that it was a vertical container, could you show a view of the tree on the left?

[Anonymous]

Hi @iAm_ManCat, 

Apologies for the delay in response - I had to step away from the project temporarily. 

I have tried wrapping the local variable with Text(), however it indicates that the datatypes are imcomparible (Number, Text) as expected. 

I have done further testing and have summarised my finding as per below - due to sensitive information I have formatted it in powerpoint and replaced list/variable names:

For whatever reason, when the lookup function is used the local variable is not recognised in a separate container regardless of whether the variable is used within the LookUp. 

Without including the lookup however, the variable is recognised. 

For this reason, when I am selecting a record in the gallery that is lined to a sharepoint list and display a set of fields corresponding to the record, nothing shows up as the default value relies on a lookup of the local variable variable 'selectedID'. 

This behaviour ONLY happens in the published version, whereas the context variable behaves as expected across containers in the PowerApps editor. 

I can only assume that this is a bug or I need to toggle a setting in one of the preview features etc. 

For now, I will have to resort to using global variables via Set as I cannot rely on using updatecontext within a screen using multiple containers. 

EDIT: Even global variables aren't being recognised via Set in a separate container via lookup. I'm going to try export the power app and reimport.