Answered

List Box Unable to pass multiline text value to control or Variable | Published app behaving differently than in editor

(0) Share

Report

Posted on by DDCJOEE

242

I have an app where my users recently started encountering errors with variables not properly displaying in labels. I was unable to replicate the error in the editor, but found that it was present when I loaded the published app in any web browser or when embedded in Teams. In order to get a better look at what was happening, I did a monitored session, but found that the code to set the variable OnSelect was indeed firing off as seen below:

{

"time": 1598383643072,

"category": "UserAction",

"name": "Select",

"logLevel": 2,

"data": {

"context": {

"entityName": "ListBox2",

"propertyName": "OnSelect",

"diagnosticContext": {

"formula": "Set(SelectedRequest, ListBox2.Selected.Request);"

}

"correlationId": "de57c7dc-7f27-4ba8-97f6-cb41e148077b28",

"controlName": "ListBox2",

"propertyName": "OnSelect",

"formulaData": {

"script": "Set(SelectedRequest, ListBox2.Selected.Request);"

}

The variable SelectedRequest, however, remains blank. I inspected the field where the variable should have shown up and found this error in my browser's console:

Indicate whether to send a cookie in a cross-site request by specifying its SameSite attribute

Because a cookie's SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevent the cookie from being sent in a cross-site request in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery.
Resolve this issue by updating the attributes of the cookie:
- Specify SameSite=None and Secure if the cookie should be sent in cross-site requests. This enables third-party use.
- Specify SameSite=Strict or SameSite=Lax if the cookie should not be sent in cross-site requests
AFFECTED RESOURCES

6 cookies
2 requests

ping?UA=0&cid=8d738ca7-c741-8d14-dad7-61296999d13e…dUeVWuWXWxrpRnhSxyBh8FTkWBo.&app=&_=1598383432790

ping?UA=0&cid=8d738ca7-c741-8d14-dad7-61296999d13e…dUeVWuWXWxrpRnhSxyBh8FTkWBo.&app=&_=1598383432791

- Learn more: SameSite cookies explained

I tried to find answers as to how I could resolve this, as I believe it is what is preventing the live app from behaving as it does in the editor. However, I cannot find any documentation this error relating to PowerApps. Has anyone else run into a similar issue?

Categories:

Building Power Apps

I have the same question (0)

All responses (9)

Answers (1)

Sort by

DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

Another thing that is interesting, and maybe this is have an impact on the published app, too, is that it loads a different version than what is considered the current "Live" version of the app.

Loading it in a web browser shows version 3.20082.17
However in the editor, it is marked as version 3.20082.19

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

Another thing that is interesting and that may be playing a role. When I click to trigger an action that should set the variable in the editor, I get this:
{
"time": 1598386335070,
"category": "UserAction",
"name": "Select",
"logLevel": 2,
"data": {
"context": {
"entityName": "ListBox2",
"propertyName": "OnSelect",
"diagnosticContext": {
"formula": "Set(SelectedRequest, First(ListBox2.SelectedItems).Request)"
}
}
},
"correlationId": "1c8d0e7d-bd2a-4b82-a534-70d37bd9d35839",
"controlName": "ListBox2",
"propertyName": "OnSelect",
"formulaData": {
"script": "Set(SelectedRequest, First(ListBox2.SelectedItems).Request)"
}
}

However, when I click it in the published app, I get this:
{
"time": 1598386354449,
"category": "UserAction",
"name": "Select",
"logLevel": 2,
"data": {
"context": {
"entityName": "ListBox2",
"propertyName": "OnSelect",
"diagnosticContext": {
"formula": "Set(SelectedRequest, First(ListBox2.SelectedItems).Request)",
"span": {}
}
}
},
"controlName": "ListBox2",
"propertyName": "OnSelect",
"formulaData": {
"script": "Set(SelectedRequest, First(ListBox2.SelectedItems).Request)"
}
}

Same control, same function executing, however, there are a couple of differences between the details. In the published app, there is an extract section in diagnosticContext called "span" which appears to be blank. In the editor, however, where it works as expected, there is an added section to the details called correlationId:
"correlationId": "1c8d0e7d-bd2a-4b82-a534-70d37bd9d35839"

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

After more extensive testing, I believe the core of the issues here is the selected/selecteditems property of the ListBox I am using. I can set variable with other methods, but any action involving the Selected/SelectedItems property of the ListBox seems to result in a blank value, whether I try to use that property itself as a value or I try to set it as a variable. Are there any known issues surrounding these properties?

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

Alright, I think the issue may be with my List Box itself or maybe the data it is housing. I tried adding a new List Box and have a label tied to each one. The label tied to my existing List Box has a Text value of ListBox1.Selected.Request, which works in the editor but not in the published app. Meanwhile, I made a new List Box that's simply using the default sample data in it, and its connected label has a text value of ListBox2.Selected.Value. This one works in both the editor and in the published app.

The only real difference between these two List Boxes is the data and some properties like Visible, DisplayMode, etc. My guess is it must be tied in some way to the data? It houses a local collection inside fo an AddColumns formula:
AddColumns(
TheseContentRequests,
"Y",
Switch(
Value,
1,
70,
2,
112,
3,
150,
4,
190
)

Would this, perhaps, cause an issue with the published app recognizing the selected/selecteditems property in the published app but not the editor?
)

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

I've confirmed by changing the data that it is not the AddColumns function that is preventing it from working in the published app. At this point I truly have no idea why I am running into this issue. On paper everything is working, but in the published app, it just won't work. There's no error I am receiving, no indication anywhere that it wouldn't be working, but it just isn't. The strangest part is that this was working as of yesterday, but without publishing any changes to the app, it just stopped working for all of my users without any reason as far as I can see.

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

I finally be onto something: I now have four labels set up, with each one capturing one of the columns in the List Box. Every one of them works, except the Request column, which is a multiline text field. It appears that PowerApps has lost the ability to recognize multiple lines of text inside of my collection/List Box Data.

Here it is working in the editor:
And then not working in the published app:

Again, the strangest parts of this are that it works in the editor, but not the published app, and that it suddenly just started completely at random with no updates having been made to the app. It's like something just changed on the PowerApps platform and started impacting the app.

Was this reply helpful? Yes No
Verified answer

DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

What's even more interesting is that I can pull the request field directly from the collection, but trying to pull it using the selected value of the List Box does not work. So it appears that the root of the issue is that List Boxes cannot pass multiline text fields anymore as a value to controls or variables.

Was this reply helpful? Yes No
DDCJOEE 242 on at

Like
a
(0)

Report
Copy link

Link copied!

In the future, when updates like this are made to the platform, it would be best to notify users as this had a significant impact on my app, my process, and unfortunately, has impacted by business's operations for the day.

Was this reply helpful? Yes No
Dan007 32 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm experiencing something similar, embedded teams app (and the direct link tot he app) has the changes I made 2 weeks ago but when I edit the live app parts of my code are missing. Any idea why ?

Was this reply helpful? Yes No