Bug (AppSheet support team it is claiming it is not a bug, but It is "by design".... (x.x)....

[Koichi_Tsuji]

I hope we could get the consensus from the majority of this community member that this is BUG (or at least buddy behaviors) while the AppSheet support desk reverted to us this is not a bug, but "by design".

Simple story.  Once we change the data type to REF, File, Image, URL or other where we expected the inline system generated action is going to be attached to those files. However, we have been seeing this odd behavior for long time and have been reported to the support desk. However, as I personally reported here in this community, the support desk members (regardless of the languages they use, Japanese or English), they sadly do not understand what the real problem is even after we politely explained to them.  Finally they concluded "this is by design"....  The word we have to call everyday after contacting with AppSheet support desk is just sadly "what a bloody day today..."! All of our effort once again in vain...

There are other cases, but this is one of example.

Back to the details of "bug" as far as we believe.

As you see, once we change the data type to the ones which would create the new system generated actions, and save the editor. The new inline action is generated. However, the attaching column is unselected. Hence, we have to manually correct those every single occasion. Just tedious.  And not friendly for new AppSheet creators.

To make the story worse and complicated, after the new inline action is generated (target column is unselected). However, we reload the browser, the target column is oddly selected..... 

On this earth, in my opinion, this is perfect bug, but Google/AppSheet support official opinion is "this is what we expected and intend" which led to their own conclusions to us. 

Annoying and no hope.

@AleksiAlkio @devingu @lizlynch 

[Koichi_Tsuji]

We have bunch of problems with AppSheet to seamlessly operate our daily business workflow. However, once we noticed the bugs or glitches, it takes months or years to let the support desk to understand what the problem. If we are lucky, the case is escalated internally to next phase. However, after the "specialist review", then they always come back to us with just surprising answers. 

Hence, I promised to myself we never get in touch with support desk, but we speak loud here in this community, which may give us fuel to address and correct the AppSheet world.

[MultiTech]

Pretty sure this centers around the inter-office politics that Praveen exposed.

Support said this is by design - but clearly... this is something that a user would perceive as a bug.  When you do something that would otherwise cause a thing to happen, but in this instance it doesn't - we often think of that as something "not working correctly."

So there is clearly something that's not 100% smooth here... In a perfect world there would be some sort of deeper kind of reset for that particular drop-down that's not quite getting it during the regular save cycle. It gets it when you do a refresh, which means there's some sort of mechanism behind the scenes that could do that update on the fly... Someone just didn't put that in the mix.

So why would support be stubborn about this?  Why defend the current behavior, instead of admitting the issue and moving forward?

If you take into consideration the fact that, apparently, if you merely upset someone at Google - they can go and tattle on you to HR, and possibly get your fired (at the worst).  So when you consider that THAT is the environment in which all of the employees of Google are working under... it makes sense that someone would "defend" another engineers work, despite the fact that it's clearly not the optimal way.

• Don't wanna upset anyone.  Might loose my job.

Operating under conditions like that would be incredibly stressful, and really cognitively draining; every action you take has all of these consequences and ripples that you have to take into consideration. Once I found out what it was really like, I don't envy any of the engineers or anybody anymore and actually have sympathy for their plight. Plus then you have everybody in the community piling on, and there's not really anything that the devs can do about it because.... You know.... Minefield.

You can read more about what Praveen found when he was brought into the fold at Google here.  https://pravse.medium.com/the-maze-is-in-the-mouse-980c57cfd61a

[Koichi_Tsuji]

Thanks mate.

You nicely translated my poor English to proper English. I fully agree with you.

Not sure if or not "You are fired" is hot topic or not in Seattle (US?) or not, but better to server to the customer first, which we never feel from Google.

I just share what the Google s ten things 

https://about.google/philosophy/?hl=EN

Unfortunately in my opinion, 10 target never achieved (as far as AppSheet is concerned) . 

Again in my opinion.

[Rifad]

---

@MultiTech wrote:

If you take into consideration the fact that, apparently, if you merely upset someone at Google - they can go and tattle on you to HR, and possibly get your fired (at the worst). 

---

If this is true thats soo stupid. They need better managers.

[Rifad]

---

@Koichi_Tsuji wrote:

but better to server to the customer first

---

They don’t serve to developers like us. Consequently, end users and businesses will be affected. We wouldn’t comment here if we hadn’t developed an app for years to witness the current ‘drama’ that Google inflicts on users. The manager of Google should be fired first, and someone bold should take action. This appears to be a trivial matter. As long as I have to manage my existing apps and clients, I will continue to criticize them. Business shouldn’t be affected by their internal politics. Once I leave this, as I’ve mentioned before, I will move entirely to different platforms.

Apologies for being rude to those who chat with us in support; their responses are truly foolish.