You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

May 19, 2017

The issue affecting projects using User Properties has been resolved for all domains, although forms that were edited between Wednesday afternoon (EDT) and Friday around 10PM EDT may have sustained User Property loading issues that will need to be reviewed and corrected manually. If you notice issues with User Properties not loading as expected, please email support@dimagi.com and we will provide as much information as we can to help you determine if your app is affected and how to fix it.

Technical details of the types of issues you may observe if you have edited a form using User Properties between Wednesday afternoon (EDT) and Friday around 10PM (EDT): User Property loading was migrated into the Default Value field of questions into which User Case Properties had previously been loaded. Your app may not build until you fix the issue(s); this will happen if a User Property that was loaded into the form did not have the same name as a regular Case Property in the module's case. Alternately, your app will load a Case Property with the same name as a corresponding/expected User Property, if such a Case Property exists; app builds will succeed but the wrong value will be loaded into your form. In general it is recommended to review all questions where a User Case Property was loaded into a form and verify that the expected User Property (having a hashtag path starting with #user/ ) is present in the Default Value field.

May 18, 2017

Currently, there is a known issue affecting some projects who user user as a case in their apps. If your app is potentially affected, you will receive an in product alert via the red alert bell.

This issue involves user case properties not being loaded correctly into a form. Forms may not work correctly, and you may see error messages or may not notice that something is broken. 

Any app that is potentially affected will receive an in product alert. If you see this, and your app uses user as a case, please hold off on making any edits or deploying a new build until this is resolved. Apps with no in product alert, and/or that do not use user case are not affected. We apologize for any inconvenience and are working as quickly as possible to resolve this issue.

 

For a list of past maintenance updates, please visit CommCare Maintenance Updates – Archives

  • No labels