I’m trying to make use of the PATCH functionality to simplify a deployment and it looks to get all but finished, and then barfs the following error:
HTTP Status 500 - Request processing failed; nested exception is org.hibernate.HibernateException: identifier of an instance of org.hisp.dhis.dataentryform.DataEntryForm was altered from 2212129 to 0
The command I’m running is the following (I’ve obfuscated certain elements)
I’m trying to make use of the PATCH functionality to simplify a deployment and it looks to get all but finished, and then barfs the following error:
HTTP Status 500 - Request processing failed; nested exception is org.hibernate.HibernateException: identifier of an instance of org.hisp.dhis.dataentryform.DataEntryForm was altered from 2212129 to 0
The command I’m running is the following (I’ve obfuscated certain elements)
I think you might have to do a full update of the object. PATCH functionality is a bit flaky at the moment, and really only works with simple properties (strings, numbers etc).
I’m currently building a new importer for 2.23/2.24 and I’m hoping to have a much more robust PATCH functionality there (probably for 2.24)
Please also note that this object changed in going from 2.21 to 2.22, and data entry forms are now what we call an id object, which means it needs to be referenced instead, and we have a endpoint called /api/dataEntryForms for it
I’m trying to make use of the PATCH functionality to simplify a deployment and it looks to get all but finished, and then barfs the following error:
HTTP Status 500 - Request processing failed; nested exception is org.hibernate.HibernateException: identifier of an instance of org.hisp.dhis.dataentryform.DataEntryForm was altered from 2212129 to 0
The command I’m running is the following (I’ve obfuscated certain elements)
Good to hear that PATCH is getting a facelift in 2.23/2.24. We ended up doing a full update on the object with the preheatcache set to FALSE (saved a lot of time).
Question about the dataEntryForm, are you saying that these are now completely separate objects to dataSet? As in, the dataSet will reference a dataEntryForm just like it would reference a categoryCombo?
···
On Wed, Mar 23, 2016 at 11:11 PM, Morten Olav Hansen morten@dhis2.org wrote:
Hi
I think you might have to do a full update of the object. PATCH functionality is a bit flaky at the moment, and really only works with simple properties (strings, numbers etc).
I’m currently building a new importer for 2.23/2.24 and I’m hoping to have a much more robust PATCH functionality there (probably for 2.24)
Please also note that this object changed in going from 2.21 to 2.22, and data entry forms are now what we call an id object, which means it needs to be referenced instead, and we have a endpoint called /api/dataEntryForms for it
I’m trying to make use of the PATCH functionality to simplify a deployment and it looks to get all but finished, and then barfs the following error:
HTTP Status 500 - Request processing failed; nested exception is org.hibernate.HibernateException: identifier of an instance of org.hisp.dhis.dataentryform.DataEntryForm was altered from 2212129 to 0
The command I’m running is the following (I’ve obfuscated certain elements)
Yes, just refer to it like you would with any other object reference (we
also now have /api/dataEntryForms)
···
On Wed, Mar 30, 2016 at 9:27 PM, Timothy Harding <tharding@baosystems.com> wrote:
Question about the dataEntryForm, are you saying that these are now
completely separate objects to dataSet? As in, the dataSet will reference a
dataEntryForm just like it would reference a categoryCombo?
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
