Recently we have encountered issues where the value being shown in the Detail view is not the same as the value being shown in the Edit/Form view.
The issue is with virtual fields.
This should be impossible, as they are meant to be the same thing.
I troubleshooted it the first time we encountered this and found that using:
[Field]=""
instead of:
ISBLANK([Field])
caused the issue.
However, now I have the same issue when using a SELECT formula.
This time the field is blank in Detail view, and then has the correct value in Edit view
Every time I have encountered this issue, the correct value is shown in Edit view.
However, other parts of the app read the value in the Detail view - so it's a major issue.
Seems like a very major issue.
I have reported to Appsheet, but they are taking there time to get back to me.
Wondering if others are experiencing the same thing?
Hi @Tom_Graham
@Tom_Graham wrote:
I have reported to Appsheet, but they are taking there time to get back to me.
Common problem at this time, unfortunately 🙂
@Tom_Graham wrote:
I troubleshooted it the first time we encountered this and found that using:
[Field]=""
instead of:
ISBLANK([Field])
caused the issue.
You should stick with ISBLANK() expression 🙂
@Tom_Graham wrote:
However, now I have the same issue when using a SELECT formula.
Can you please share the detailed expression you used, along with some screenshots to illustrate the situation you are facing with your two expressions?
Hi @Aurelien
Thanks for the reply and confirming it's a known problem - worrying to hear it's a common problem though!
Noted that should use ISBLANK() - have been doing this for a while, but we would have many old formulas still using ="" still... would be good to know if we have to go back through and change them all. Though at present, seems it still works in most circumstances.
Below is one of 2 current examples I have
- "Current Match Live Price Check" is blank/empty in Detail view, but has value in Edit/Form view.
- the "Current Match Live Price Check2" field is basically identical formula but taking the data from a different table. It's working correctly.
Noting that if you create another formula based on "Current Match Live Price Check" field, it will read it as Blank. $525 is the correct value.
UPDATE
I realised that I had used extra brackets in the working fields formula.
After adding the extra brackets around the first condition, it is now working (showing $525 in both circumstances)
I know Appsheet suggested these brackets in some instances when using SELECT (I think when using [_THISROW]. Though still strange that it gives different results in Detail and Edit view.
UPDATE
Actually, that did not solve the issue.
After editing the formula, the preview in the App updates and shows the value in Detail view. But after you save the app, it then reverts to not showing the value again.
ok, thank you for the addtional information. I'm not a huge fan of extras brackets myself, I use it only when my expression doesn't return the expected result 😂
@Tom_Graham wrote:
Actually, that did not solve the issue.
After editing the formula, the preview in the App updates and shows the value in Detail view. But after you save the app, it then reverts to not showing the value again.
This is curious.
Are the columns "Current Match Live Price Check" and "Current Match Live Price Check2" both real columns?
Please note that if using a real column, value will update only when saving a form.
They are both virtual columns.
User | Count |
---|---|
35 | |
11 | |
3 | |
3 | |
2 |