[Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hey team, We are setting up a new instance of DHIS. We had got already an instance running. So we exported metadata from there and imported in new one. But If we see, we are getting a difference between few *IDs, (*e.g.- category-option IDs) for few reports. What I think because we have used the

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Lars Helge Øverland
Another explanation is that the category option combos for some reason were not part of the exchange file, and was later re-generated in the destination system. This will give different UIDs. Let me know.. On Tue, Jul 14, 2015 at 10:47 AM, Lars Helge Øverland larshe...@gmail.com wrote: Hi

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Lars Helge Øverland
Hi Mritunjay, are you referring the the internal database identifiers, or the UIDs (stable identifiers) ? The UIDs will (should) not change and this has nothing to do with the build. The database ids will likely change when you do an export followed by an import. When writing reports you

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Bob Jolliffe
Hi Mritunjay As Lars says, if the categoryoptioncombos were not exported then that would indeed have caused a problem. And/or if you were using internal primary keys in your reports. But is there a particular reason you need to rely on the import/export functionality to do this? Did you try