New Bug Encountered: Format with CONTEXT("ViewType") not working properly

I’ve made an app to demonstrate the issue I’ll describe here. It’s called “Format test” and can be found here.

https://www.appsheet.com/portfolio/230844

What I want to do is make the Japanese column big in the detail view but not in the deck view. So, I used the following condition:

It works at first:

29

But when I navigate from the table to the detail view, it no longer works:

38

59

By the way, I was also unable, in a different app, to get it to distinguish on the basis of the view name. In either case, the app seems to “remember” the format that it applies to the table view and does not adjust when the user navigates to the detail view.

Thanks in advance. I hope this can be fixed easily.

Even though I’ve been using AppSheet for a while and should know how to share a prototype on my “free” account, I still wind up getting messages like this. I’m requiring sign in, but I’m the only user and I expect people to copy my app if they want to look into it in. If someone could help my understand the proper procedure for sharing prototype apps on a free account, I’d appreciate it.

Hi @Kirk_Masden I posted a tips and tricks, hope that helps. App needs to be deployed. Profile apps are free.

1 Like

By the way, it’s interesting to me that the order of operations seems to make a difference.

  1. Start with the table
    48
  2. Tap to view
    56
  3. Tap on the refresh icon
    05

@morgan Any thoughts?

This suggests a format rule’s condition is evaluated only at sync-time, not dynamically as the user interacts with the app. Similar to the way an app formula is only evaluated on sync (except in forms).

I can confirm that other format rules work without syncing. Also, even after the refresh (sync), if I navigate back to the table view and then tap on one of the records to view the detail view, I’m back where I started – the format is gone again. So, I think it’s a matter of some kind of influence that the table view has on the related detail view that follows it – not just sync issues.

For now, I’ve resolved the problem by using a VC column to make a duplicate of the column I need to format differently in different contexts. This has allowed me to make format rules that are not dependent on context (“Make column A normal size and make column A-VC big” etc). I just need to decide which column to make visible in various views. Still, it would be nice if context expressions worked reliably in format rules.

1 Like

Recently, I have been avoiding “context” expressions with format rules. Instead, I make virtual columns that I only use in contexts where I want the rule to be applied and then make a format rule just for that virtual column. That seems to work well.

1 Like