I’m running into an issue with entity properties on different versions of ODK Central and I’d appreciate some guidance from the community. I’m currently working with two environments:
Issue
In my on‑prem server (v2025.4.2), entity properties that get their values from a calculate field work perfectly. However, on the cloud server (v2025.4.4), the same forms do not populate entity properties when the value comes from a calculate field.
This was unexpected because the forms passed testing on the dev server, and I now need to deploy them to production urgently.
Question
Has anyone experienced this issue in v2025.4.4?
Is this a known change, bug, or regression?
And is there any workaround while waiting for a fix?
Any insights would be greatly appreciated.
Thanks in advance!
Hello, I think this is related to what I also just posted this morning, although I had not identified calculations were the root cause since I only had calculations as entity properties in this form (and actually I now realise that the form I believed was working had been working with 4.2 and indeed the calculation property has broken since I updated to 4.4) Multiple entity behaviour - difference observed between ODK central and ODK Collect - Support - ODK Forum
Are you observing this only when updating entities or also when creating entities?
It seems to me the issue may be only with updating existing entities
I do not have a workaround for this unfortunately, but maybe others will be more helpful there
For me, this issue appears during entity creation. As shown in the images below, the older version correctly generates two entity properties, but in the newer version I only get one property instead of both.
@Chimwemwe This is an issue with the conversion from XLSForm. So if you have an XForm that's working in your test environment, you can download that and upload it to your production instance and that should give you the behavior you want.
Thank you @LN. I tried using the XForm version and it worked perfectly. I also received a quick response from support confirming that the issue has now been fixed. Really appreciate the great work you’re all doing to keep improving ODK!
Thanks so much for the follow-up @Chimwemwe and I'm so glad you're back up and running!
We traced this back to an issue with our Cloud upgrade process for v2025.4.4. If any other Cloud customer has been affected by this, please get in touch so we help make sure all your Entities have been correctly created and updated.
Self-hosters were not affected by this issue.
It looks like @Thalie is experiencing something different, I'm still looking into it and will update on the other thread!
Actually now that I have checked everything, that previous form is working as expected. I misread the dates when browsing for changes in entity entries (this is a sparse dataset, not all participant entities being updated), the entries that were missing entity property calculations were actually from a former and not from a later version (i.e. before I moved entity properties in the same group with 4.2). I had missed those entries when I made targeted manual correction. All the most recent entries are either complete as expected or either empty also as expected by process. So all good on that front.
,
