Data Refresh Problem when Navigating between Screen

[MarcBailey]

When navigating using the OnSelect function (creating var to pass value) occassionally the data in the navigated to Screen does not update.  If I navigate back and then navigate to the Screen again then the data is correct.  I am not sure, but it is if sometimes the var does not post before the to Screen displays. 

Any help would be greatly appreciated.

Thanks, Marc

[MarcBailey]

Hi Sienna,

It is strange that it works fine when running the exact same App on my Desktop but when I run it on my Mobile Device the problem occurs.

The Data = AcctLog (Sharepoint List)

Thanks again for reviewing this, Marc

[Sienna]

Yes but that is usualy a sign of something is wrong with the app. What warning does it say when you hover on the blue exclamation mark right next to your item property?

[MarcBailey]

Blue Exclamation Mark = Suggestion: Part of this Search formula cannot be evaluated remotely due to service limitations. The local evaluation may produce suboptimal or partial results. If possible, please simplify the formula. For more information, please see the Search function documentation.  The Blue Exclamation Mark refers to the = sign and "LognNote" - I showed them in blue in the formula.

SortByColumns(Search(Filter(AcctLog,AcctID=Value(CurrentAcctID)),TextSearchBox1_4.Text,"LogNote"),"DateEntered",Ascending)

[Sienna]

So we are getting somewhere finaly 😉 Fix this and your app will work. I’m not sharepoint expert so I will be more guessing here. From previous post I know that there is a bit diferent syntax. Try to remove everything up to AcctID then type “.” And it should suggest you options what you can use. I think it should be something like AcctID.Value.ID = ... or something

[Sienna]

That means also LogNote should be specified a bit diferently... I guess..

[MarcBailey]

Sienna,

Thank you so much for sticking with me on this.

In attempt to recode according to your suggestion, I was unable to because there is available code options after the AcctID. as shown in the attached pic.  I'm not sure what the syntax would be to correct this.  The AcctID is a column in AcctLog (Sharepoint List). This column's value is created when a new Account Log is created using the AcctMain ID for the selected account (CurrentAcctID). I assume it is not letting me enter AcctID.Value because it is not a lookup column.

The AcctID value is what allows the filter to match the AcctID with the CurrentAcctID so that it knows to display the matched values.

In addition, in the code I changed the = sign to    in    and it eliminated the "LogNote" blue exclamation error.  But when running App on mobile device I still get the same error of displaying the previous data not current data.

I'm not sure if all this background info helps or is just interference.

Let me know your thoughts.

Greatly appreciated - Thanks, Marc...

[MarcBailey]

Correction:  I was unable to because there is no available code options after the AcctID. 

Sorry - I left off the no.

[Sienna]

That is ok.. Like I said I can only guess here. 

Try to look at this thread

https://powerusers.microsoft.com/t5/General-Discussion/Error-Cannot-use-record-values-in-this-contex...

That should give you an idea how to filter sharepoint list

Also I would definitely try to change the variable Value(CurrentAcctID) with a number only and if that will work then you know that something is wrong with the variable syntax. If you pulling the CurrentAcctID variable from sharepoint then you might also set it with .something.  Try to display that variable in a label what it shows you

And also get rid of the Search and SortByColumns function for now and try to concetrate on that filter first. When that will be correct then add another functions in there

[MarcBailey]

Sienna - thanks for the link and all of the help.

I was able to determine the Blue Exclamation Error for the = sign was because the AcctID column type in Sharepoint was a Text field and the CurrentAcctID variable is a number - therefore they were incompatitable creating the error.  I changed the column type in Sharepoint for AcctID to number and it corrected the error for the = sign.  Now I have to figure out the reason for the error on "LogNote" that has reoccured.  I am pasting several post that I just read that I am going to review and see if they might be related:

Note from Microsoft Employee in Forum: Related to Blue Error Messages:

You can use the Text() function to transform a value to text and Value() to convert text to a number. Depending on the behavior you want from the search box, you can either use StartsWith() and convert the ID to a Text value and allow a broader set of matches or you can convert the search text to a number and look for exact ID matches.

Limitation Post from Microsoft Employee in Forum: Related to Blue Error Messages:

So, I asked around and it seems like Sharepoint has a known limitation that prevents it from searching a numerical column. Since this function can't be delegated to the server, PowerApps does the best it can and attempts to download the first 500 rows from the data source and perform your filter operation locally. I suspect that you have a large data source and the rows you are interested in are not in the first 500, therefore the search comes up empty handed. To work around this, it's possible to create a new column in Sharepoint that's a text version of the ID and perform the filter on that column instead. I hope that is sufficient for you, even if it is an ugly solution.

If you have any further thoughts or have time to review further please update me.  In the meantime, I will update on the progress I make.

You have been extremely helpful and I am greatly appreciative.

Thanks - Marc...

[Sienna]

You're welcome. At least I tried 🙂 I'm glad you have fixed the filtering error. My guess on the LogNote would be on the type of the column in sharepoint or something with that. It might be also because of that sharepoint limitation. But I might be completely wrong. I have never even work with sharepoint so it is impossible for me to say.  I have noticed you have created new ticket just for that issue so hopefully someone will finally find a solution for it. I'll keep an eye on it.

Good luck