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 just taking a copy of the old database and running the new war file against it? That tends to be very reliable. The best place to look for historic builds is https://apps.dhis2.org/ci/. For each release number you will see that there is a build history which maintains (a limited number of) previous builds. Cheers Bob On 14 July 2015 at 09:58, Lars Helge Øverland <larshe...@gmail.com> wrote: > 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 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 should base it on the UIDs just for this reason. >> I am guessing you relied on the database identifiers which then changed >> during import-export. >> >> regards, >> >> Lars >> >> >> On Tue, Jul 14, 2015 at 8:16 AM, Mritunjay Dubey >> <mritu...@thoughtworks.com> wrote: >>> >>> 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 same metadata it should be same in >>> both. >>> >>> BTW we have different Build Revision in both instances. So if there is a >>> way to get the artifacts of previous builds, it might solve the problem. >>> >>> Kindly let me know. >>> >>> Thank you >>> Mritunjay Dubey >>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~dhis2-devs >>> Post to : dhis2-devs@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~dhis2-devs >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> >> -- >> Lars Helge Øverland >> Lead developer, DHIS 2 >> University of Oslo >> Skype: larshelgeoverland >> http://www.dhis2.org >> > > > > -- > Lars Helge Øverland > Lead developer, DHIS 2 > University of Oslo > Skype: larshelgeoverland > http://www.dhis2.org > > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : dhis2-devs@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
