Patched values in collection don't appear as expected

[lmheimendinger]

I am befuddled by the behavior of one of my apps.

1. I create a collection from a data source that gets a single record.  That works great.
2. From the gallery that uses that collection, I am displaying name and address information with an icon to edit it.  I gather the lines into a concatenated string and display in a rectangular label.  Again, works fine.
3. When the edit icon is clicked, I navigate to a screen that displays the existing info as default values in text input controls.
4. A save button then patches the text control values into the collection, and then repeats the concatenation process and returns to the display screen.
5. Alas, the label still shows the OLD N/A values.  However, if I click on the edit icon again, do nothing to modify the values but save again, lo and behold the correct values appear.

If I stop running the app after I make the changes and save them, the collection shows the CORRECT DATA THAT WAS CHANGED!  

Here's the save button onselect values

Here is the text value for galSelectedCust.Selected.lblShip1.Text

If you are going to suggest that I patch the data source and then collect the record again, let me save you the time to reply.  The app is not trying to permanently change the data but allow it to change only for the lifetime of what the app does.  In other words, the app grabs the shipping N/A from the data source but allows it to be changed for only what the app does, not for the data source itself.

Thanks in advance if you can help solve this clumsy process.

[WarrenBelz]

Hi @lmheimendinger ,

This sounds like a refresh issue - have you looked in View > Collections > colCustomer after the first run and see what value is in the field?

[lmheimendinger]

Yes I did.  After the "first save click" I stopped playing the app, viewed the collection and the field values matched what the patch did.  But it didn't redo the set concatenate string until the 2nd save click.  

[WarrenBelz · Accepted solution]

Hi @lmheimendinger ,

Why not simply do this?

With(
  {
     wAdd1:txtShipHdrl.Text,
     wAdd2:txtShipHdr2.Text,
     wAdd3:txtShipHdr3.Text,
     wAdd4:txtShipHdr4.Text,
     wAdd5:txtShipHdr5.Text,
     wDuty:txtShipCity.Text,
     wState:txtShipState.Text,
     wZip:txtShipZip.Text 
   },
   Set(
      varShipAddr,
      If(!IsBlank(wAdd1),wAdd1) &
      If(!IsBlank(wAdd2),Char(13) & wAdd2) &
      If(!IsBlank(wAdd3),Char(13) & wAdd3) &
      If(!IsBlank(wAdd4),Char(13) & wAdd4) &
      If(!IsBlank(wAdd5),Char(13) & wAdd5) &
      wCity & wState & wZip
   )
)

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.

Visit my blog Practical Power Apps

[lmheimendinger]

Although there were a few typos in your response, it did indeed work.  Many thanks.

I have another post about a similar issue:  combo box for selecting a customer.  When I type characters and then click on the customer dropdown, none of the Set commands seem to work although I can stop playing  the app and see that they "DID" work.  It's not until I click on the combo box again (doing nothing else) that the fields populate on the screen.  Should a similar approach work?  Why would WITH do this and not just a SET by itself?

Regardless thanks for the help.

[WarrenBelz]

Hi @lmheimendinger ,

Typos where because you posted an image, not Text and I had to OCR it (please try to do this in future as it is much easier to correct / modify). With() statement is only to shorten the code at the bottom.

[lmheimendinger]

No problem at all thanks again.

I may have discovered something: when I simply run the app instead of playing it  from edit, this issue doesn't seem to occur.