Hi all,
I’m hitting an error with OData v4 data sources whenever an entity set declares a composite key, and I’d like to know if others see the same thing or if I’m missing something.
What happens
- AppSheet reads
$metadataand generates the table correctly, including the virtual_ComputedKeycolumn (CONCATENATE([A],": ",[B])). - When it loads the data, the app fails with:
Unable to fetch app definition. Error: Data table 'OrderDetails' is not accessible due to: Sequence contains no elements.(the same error appears with View data source in the editor). - Once a table like this is in an app, other tables added to the same app can fail with
App '…' version … is not runnable— a new app with only a single-key table works fine.
Easy reproduction with a public service (no real credentials needed)
- New OData data source, service root
https://demodata.mescius.io/northwind/odata/v1/(Basic Auth with dummy values;$metadatadeclares OData 4.0). - In a new app add
OrderDetails(key =OrderId+ProductId) → the error above. - In a separate new app on the same data source add
Products(single keyProductId, 77 rows) → loads fine.
What I verified on my own OData service
- Server logs show AppSheet requesting
$metadataand then the entity set, and every response is HTTP 200, fully delivered. So the failure happens after AppSheet received the data. - With a composite key it fails even with only 100 rows, with only 5 columns, and with made-up data; it makes no difference if the data source is new.
- The very same rows with a single key column load fine, including the full table (~30,000 rows, ~52 MB uncompressed).
- The composite key was declared the same way when it worked: the table loaded correctly until around midday on 2026-11-06 and then stopped, apparently after I deployed changes to the service. Reverting them did not bring it back, and any new data source shows the same error today. So I can’t tell whether something changed on the AppSheet side or whether I broke something.
Workaround that worked for me
Expose a single key column instead of two. I added an Id column with the same value _ComputedKey had (A: B), declared it as the only <Key>, regenerated the table structure in the editor, set Id as key and deleted _ComputedKey. The app works again.
Questions
- Has anyone seen “Sequence contains no elements” with OData tables that have composite keys, and did it start recently?
- Are composite keys in OData feeds supposed to work? If not, is a single key column the recommended approach?
- If someone from the AppSheet team can look at it: app
TestComputedKey-164949846, IDc40d38a1-8fc9-436d-aeae-71e1435e336a.
Happy to share more details (logs, $metadata) if useful. Thanks!
