Re: [Dhis2-users] Has metadata import stopped working?

Thanks for the clarification, Morten. Regarding the last question, no, there was no feedback when it failed, only the hibernate-exception in the tomcat log. In the GUI, it was just stuck indefinitely on "importing X objects…" This was 2.27 btw. Olav 12. apr. 2018 kl. 11:09 skrev Morten Olav

Re: [Dhis2-users] Has metadata import stopped working?

On Thu, Apr 12, 2018 at 1:54 PM, Olav Poppe wrote: > Hi, I managed to solve the problem in the end. It was indeed caused by > one single object being shared with a group I had not included in export… > Good I’m still left with some questions though: > - even with

Re: [Dhis2-users] Has metadata import stopped working?

Hi, I managed to solve the problem in the end. It was indeed caused by one single object being shared with a group I had not included in export… I’m still left with some questions though: - even with skipValidation=true the import failed until I identified the extra user group - is that a bug,

Re: [Dhis2-users] Has metadata import stopped working?

Hi Olav I see that you include sharing in these payloads, are you sure all user groups and users are included? did you try with skipSharing=true ? skipValidation is not really recommended, as it will not validate anything.. but still requires things to be correct (if its not, it will result in

Re: [Dhis2-users] Has metadata import stopped working?

Thanks, JM. This is an event progrmame, so it’s not the TE. BUT I just managed to identify the culprit: One optionset was shared with a group not included in the export… Morten, is valudation of sharing not skipped even with skipValidation=true? Would be nice with some feedback on what fails..

Re: [Dhis2-users] Has metadata import stopped working?

Hi Olav I didn’t check the dates on the thread, I thought Knut was still waiting for an answer. Have you been able to determine which dependencies are affecting the import? Also, if this is a tracker program did you check if the UID of the TE is the same you have in the system? Best regards, JM

Re: [Dhis2-users] Has metadata import stopped working?

Hi, I might be creating some confusion by reviving Knut’s old thread. I heared from Knut that he resolved it by importing via the API, using the skipValidation=true option to get around dependency issues. I’m getting the same error, but in this case importing a tracker programme. And in my

Re: [Dhis2-users] Has metadata import stopped working?

Hi Knut Try splitting your import by org unit levels and do the import in order, starting with the lowest level (1, 2, 3...) The problem happens because the import creates the objects out of order in regards to dependencies, in your case an org unit before its parent. Best regards, JM On Fri, 6

Re: [Dhis2-users] Has metadata import stopped working?

Hi! I was encountering the same error when trying to import metadata with collection of other objects (parent and child relations) from the web APIs in version 2.27. *ERROR: org.hibernate.TransientObjectException: object references an unsaved > transient instance - save the transient instance

Re: [Dhis2-users] Has metadata import stopped working?

I’m having the same issue and error importing into an empty 2.27 database. Though in this case a slightly modified dependency export of a tracker programme, not orgunits. Knut, did you find a solution? Sending you the payload, Morten. Olav 12. jan. 2018 kl. 08:39 skrev Morten Olav Hansen

Re: [Dhis2-users] Has metadata import stopped working?

That sounds weird Knut, would you mind sharing the org unit payload? -- Morten Olav Hansen Senior Engineer, DHIS 2 University of Oslo http://www.dhis2.org On Fri, Jan 12, 2018 at 2:19 AM, Knut Staring wrote: > I have tried doing metadata export without sharing from 2.27 and

[Dhis2-users] Has metadata import stopped working?

I have tried doing metadata export without sharing from 2.27 and importing into 2.27, just the OU hierarchy and levels. Importing into a clean instance gives this: INFO 2018-01-11 20:16:06,750 [Level: INFO, category: METADATA_IMPORT, time: Thu Jan 11 20:16:06 CET 2018, message: (admin)