EOMONTH expression errors.

If anyone has an idea why this error is coming.

Searched the commuinty, but I could not  get any meaningful past conversation over the same error.

I suspect there is a glitch with AppSheet expression parsers, but I m not able to reproduce the same error, while this error is happening with a particular app, which is not savable.

Snag_21bd6a96.png

โ€ƒ@Steve 

Please dont ask me to post the question to the support desk. I m fed up and not willing to do so.

 

0 10 249
10 REPLIES 10

Steve
Platinum 5
Platinum 5

@Koichi_Tsuji wrote:

Please dont ask me to post the question to the support desk. I m fed up and not willing to do so.


There is no other option.

Attn @devingu 

Yes, I know @Steve 

So I zip my mouse. Stay quiet. 

Steve
Platinum 5
Platinum 5

What is the expression? The best we can probably do is devise a workaround.

EOMONTH([Date],([Month]-1))+day([Date])-1

Kinda of expression.

This expression is getting through a mock up app, but not getting through with PROD apps. Annoying

 

Im not able to REPRO the issues with other apps, but trust me this is happenning in the certain apps.

 

I did have a doubt, normal/virtual column may bring the difference (Because of Expression parser between client and server), but this assumption was wrong. 

Employing the same expression anywhere (VC or Normal) is pulling the same error which make the app not-working.

 

My guess is EOMONTH expression is causing an error.

I spent days and hours to come up with idea if we can construct the equivalent expression without using EOMONTH, which is equal to 

EOMONTH([Date],([Month]-1))+day([Date])-1

Any brilliant idea?

@Steve 

Steve
Platinum 5
Platinum 5

@Koichi_Tsuji wrote:

EOMONTH([Date],([Month]-1))+day([Date])-1


Can [Date] be blank? That might cause an error.

What are you trying to get with this expression? The use of [Month] confuses me.

Thanks @Steve 

For example, if [Date] is 31/Jan/2023 and month value is 2, then we get 30/Mar/2023 as return value for this expression.

Yes, this exprssion does this job on the mock up app, but headache is the same expression is breaking up app, make an app not usable.

 

To make things worse, I saved the same expression and App throw no error.

Then leave this app alone for a while.

Reload the app with new browser tab then it firstly throw the error.

Again I spent days to investiate and come up with workaround, but now I m at a loss.

If I report this issue to Google new dedicated AppSheet support desk, then it probably take years to solve. So I stay quiet.

Obvious answer from support desk, "We tested with our own environment, but it is working fine. Can you share your App Id????".  

I zip my mouth.

 

\

Top Labels in this Space