Critical OData connector issue since Nov 7 2025

AppSheet AppSheet Q&A
, ,
1

Hi,
I’m reporting a critical OData connector issue that has now been affecting all my AppSheet projects for more than 10 days. I need transparent communication from the AppSheet team because support has been unable to provide any real information (9-0147000039199)

1) Timeline — bug introduced on Nov 7, returned on Nov 11

  • The issue first appeared on November 7, 2025 around 9 AM (CET).

  • The same day in the evening it suddenly disappeared and everything started working again.

  • Then on November 11, the exact same isssue returned and has been present ever since.

2) Actual error

AppSheet is unable to load the OData metadata and returns:

The JSON value could not be converted to System.Boolean. Path: $.IsSAPGateway

I’m also unable to connect to the public OData services, so in my opinion it’s clearly a platform-level bug.

3) This is not the first OData connector bug

I previously reported another real bug in the OData connector (3-1951000039875).
Given how easy it is to test functionality using any public OData service, I have to ask:

Where are the unit tests?
How can a critical connector break twice and remain broken for 10+ days without detection?

This is unprofessional and unreliable for a platform that claims to support enterprise use cases.

4) Extremely unprofessional support experience

This has been the most frustrating support interaction I’ve had in years. Specifically:

a) They asked me “when did the issue start?” even though I wrote it clearly in the initial report.
b) They repeatedly asked for access to my app, even though I stated from the beginning that the bug occurs:

  • in all apps,

  • on all OData connections,

  • even with public OData endpoints.
    So there is nothing in my app that could cause this.

c) For 10 days I have received nothing but polite template replies.
No technical detail, no confirmation, no status, no ETA — not even an answer to the basic question:

Has this issue been confirmed as a platform bug — yes or no?

This is unacceptable.

5) I have trusted and promoted AppSheet for years

For the last 5 years I have:

  • Recommended AppSheet as a reliable platform to many clients

  • Delivered professional trainings

  • Built multiple production systems

  • Advocated for AppSheet even against competing platforms (including Microsoft Dynamics)

But I have never expected such poor reliability and such unprofessional communication.

My trust in the AppSheet starts getting irreversibly damage.

6) What I need now

  1. Is this bug officially confirmed?

  2. What is the cause of the error: “The JSON value could not be converted to System.Boolean. Path: $.IsSAPGateway”?

  3. What is the ETA for a fix?

  4. Why has the connector been broken for 10+ days without communication?

I am asking publicly because private support has completely failed to provide any real answers.

Thank you,
Jan

appsheet_bug
appsheet_bug715×389 127 KB

1 Like
2

Attn @Jose_Arteaga @Adam-google @ShirleyN @zito @Gil @AleksiAlkio @devingu

2 Likes
3

Thanks @Steve,

@randal, my sincere apologies for this situation. I will get back to you with an update soon.

2 Likes
4

Hello @randal,

Thank you again for reaching out. I’ve reviewed the incident details thoroughly and found some key information regarding the current situation:

  • Resolution Status: We have an active case open with the product team, and they are currently working on this issue with high priority for a resolution.

  • OData Recommendation: Please note that OData is still in its beta release phase and is therefore not recommended for use in a production environment at this time.

  • Account and Licensing: We identified that your account is currently on a free plan. OData is categorized as an advanced data source, and utilizing it as a service requires an AppSheet Enterprise license. While running the app in prototype mode may work temporarily, the differences between plan features will eventually restrict the functionality of the application and its data source connection.

  • Support Access: Please be aware that dedicated technical support is not included with free accounts.

To ensure you can continue using OData services reliably and to enable our team to provide direct assistance and troubleshooting, we highly recommend upgrading to an Enterprise license. This will provide both the necessary feature access and direct access to our support team for further assistance.

I’m sorry, I wish I could give you a better answer. I will keep you posted on any updates regardless.

1 Like
6

Hello Jose and Thank you!

This is honestly the first structured and useful information I have received in the past 10 days, and I really so much appreciate it.

I would like to explain my situation clearly and calmly, because I think there has been some misunderstanding.

1. My biggest frustration is not the bug — it is the communication.

If you had told me from the beginning:

  1. “We cannot help you because you are on a free plan,
  2. or “OData is not a priority,”
  3. or “OData should not be used in production,”

—I would have accepted that and I would find my way.

But instead, for 10 days, I received only messages saying “please wait” without any real information and questions for things I already provided or are irrelevant.

Not even a simple confirmation whether this is a bug on your side or not. That is what hurts the most.

It is very hard to trust or upgrade a product when the communication leaves me completely in the dark.

2. I expected appreciation and cooperation, not silence.

I am not reporting an issue caused by my own configuration.

I am reporting a platform regression.

I thought you might even appreciate that and shared all the findings clearly.

Instead, for 10 days, I did not receive even a simple acknowledgment.

3. Regarding OData itself

OData is not a really super complicated technology.

I implemented simple OData v4 server (NPM @randajan/odata-server) myself in a week, without AI.

This makes it difficult for me to understand why this connector has been in “beta” for more than 5 years.

I also know about several minor bugs in the current implementation — I never reported them, because I created workarounds, and I didn’t want to burden the team.

But I would be happy to share them if there is genuine interest from your side.

4. About upgrading to Enterprise

Please allow me to be very honest:

If I upgrade to Enterprise — will my app actually work?

Because if I understand this well the OData connector is broken even with public OData services and even for users who already have paid plans.

So I hope you understand why I cannot commit to buying an Enterprise license for a feature that is currently not functional.

I am more than willing to pay for good and reliable software with well support.

But I will not pay for a app that does not work, and for support like this.

5. What I still need is one very simple answer

Has the product team officially confirmed this as a platform bug — yes or no?

I am now quite sad and disappointed, because I truly believed in AppSheet. I just want clarity so I can make informed decisions for myself and my clients.

Thank you very much

3 Likes
7

Well said.

1 Like
8

Heureka it’s working!!! :slight_smile:

4 Likes
9

Thanks for the confirmation @randal,

I read the chat you had with the support team and I will make the question whether this was a bug. I’m glad it is working again though.

By all means, if there is anything I can do to further help, I’ll be delighted to be of service.

3 Likes
10

Hello Jose,

thank you very much for your message and for stepping in — I really appreciate it.

Support has now confirmed that a hotfix was deployed, and the OData connector is working again. They also mentioned that they would like me to share the additional minor issues I’ve discovered in the OData implementation, so I will pass those directly to support. They are small things, nothing critical, and absolutely not urgent.

One more thought:
It would be extremely helpful for users if AppSheet communicated when a new platform version (or component update) is being rolled out — or at least offered a way to see the current version running on the platform. Even a simple read-only build number somewhere in the UI would save a lot of confusion when debugging regressions like this.

Thank you again for your help i really appreciate that.

Also @Steve i really appreciate your help.Not only with this topic but you and your responses to many other topics helped me so much in the past :slight_smile:

6 Likes
11

As far as I remember correctly, this feature is on beta for almost a “decade”. Among other preview (beta) features, it looks like it stays as BETA forever or our entire life.

2 Likes
12

Hello @Koichi_Tsuji,

I totally understand! That kind of long-term perspective is exactly what we need to hear, and we appreciate you calling it out.

You are absolutely right, There are certain features that have spent too long in the preview phase, and we are laser-focused on moving them out.

Here’s where we need your and everybody’s expertise! Please continue to use these preview features and by all means do not hesitate to share any hiccups, rough edges, or missed opportunities.

Every bug report and suggestion you send helps us dedicate resources, clarify priorities, and ultimately, move that feature out of Beta for good.

Thank you for your candidness and continued commitment to our platform.

1 Like