← Back to team overview

dhis2-devs team mailing list archive

Re: Fwd: Deployable war for previous builds

 

Yes please fix it.

Because it's hard to know the "default" category-combo-option UID, If you
don't have database access to source instance.

Or If there is a way to get  "default" category-combo-option UID please let
me know.

Thank you



On Tue, Jul 14, 2015 at 4:30 PM, Morten Olav Hansen <mortenoh@xxxxxxxxx>
wrote:

> Yeah, I'm pretty sure this bug is still present in 2.16. Please try to fix
> it as Jason suggested..
>
> --
> Morten
>
> On Tue, Jul 14, 2015 at 5:47 PM, Alex Tumwesigye <atumwesigye@xxxxxxxxx>
> wrote:
>
>> Dear Dubey,
>>
>> Jason is right.
>>
>> I have had trouble before with a similar issue doing imports.
>> One thing I keep in mind when importing to a new instance (without using
>> a database dump) is to overwrite the "default" category option combo
>> with the one I am carrying from the existing data.
>>
>> To be safe, first import "categoryOptionCombos with depedencies" and then
>> import the rest.
>>
>> Alex
>>
>> On Tue, Jul 14, 2015 at 1:19 PM, Morten Olav Hansen <mortenoh@xxxxxxxxx>
>> wrote:
>>
>>> Could you also please provide your DHIS 2 version and build rev? we
>>> should have fixed this issue 1-2 months ago (or at least a similar issue)
>>>
>>> --
>>> Morten
>>>
>>> On Tue, Jul 14, 2015 at 5:14 PM, Jason Pickering <
>>> jason.p.pickering@xxxxxxxxx> wrote:
>>>
>>>> In this case, you should probably alter the "default" category option
>>>> combo on the destination server to match that on the source server, if that
>>>> is possible for you.
>>>>
>>>> Something like
>>>>
>>>> UPDATE categoryoptioncombo set uid = 'XXXXXXXXX' where
>>>> categoryoptioncomboid = (SELECT categoryoptioncomboid from
>>>> _categoryoptioncomboname where categoryoptioncomboname = '(default)');
>>>>
>>>> should work, where XXXXXXX is the uid of the source server.
>>>>
>>>> Clear your server cache and rebuild all the resource tables, and you
>>>> should be good to go.
>>>>
>>>> Regards,
>>>> Jason
>>>>
>>>>
>>>> On Tue, Jul 14, 2015 at 12:09 PM, Mritunjay Dubey <
>>>> mritunjd@xxxxxxxxxxxxxxxx> wrote:
>>>>
>>>>> Hey Jason,
>>>>>
>>>>> Yes, I think it's "default" category option combo, but I'm not sure
>>>>> about it. I can see in UI of dataset, it shows as "default" and the
>>>>> date-created for category option combo is the date when I set-up the
>>>>> instance.
>>>>>
>>>>> So If it's a "default" *category-option-combo, *what should I do to
>>>>> sync it between instances ?
>>>>>
>>>>> Please let me know
>>>>>
>>>>> Thank you
>>>>> Mritunjay Dubey
>>>>>
>>>>> On Tue, Jul 14, 2015 at 3:19 PM, Jason Pickering <
>>>>> jason.p.pickering@xxxxxxxxx> wrote:
>>>>>
>>>>>> Does this happen to be the "default" category option combo? If so, it
>>>>>> will be different between different instances of the database, and you will
>>>>>> thus need to sync this one manually between your instances.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Jason
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 14, 2015 at 11:43 AM, Mritunjay Dubey <
>>>>>> mritunjd@xxxxxxxxxxxxxxxx> wrote:
>>>>>>
>>>>>>>
>>>>>>> ---------- Forwarded message ----------
>>>>>>> From: Mritunjay Dubey <mritunjd@xxxxxxxxxxxxxxxx>
>>>>>>> Date: Tue, Jul 14, 2015 at 2:58 PM
>>>>>>> Subject: Re: [Dhis2-devs] Deployable war for previous builds
>>>>>>> To: Lars Helge Øverland <larshelge@xxxxxxxxx>
>>>>>>>
>>>>>>>
>>>>>>> Just adding to that
>>>>>>>
>>>>>>> We had selected every metadata other than *Validation-criteria &
>>>>>>> Report Table.*
>>>>>>>
>>>>>>> And while importing I could see
>>>>>>>
>>>>>>> Importing 404 CategoryOptionCombos
>>>>>>>
>>>>>>> So it should not be re-generated.
>>>>>>>
>>>>>>> Thank You
>>>>>>>
>>>>>>> On Tue, Jul 14, 2015 at 2:52 PM, Mritunjay Dubey <
>>>>>>> mritunjd@xxxxxxxxxxxxxxxx> wrote:
>>>>>>>
>>>>>>>> Hey Lars,
>>>>>>>>
>>>>>>>> For us, the second explanation seems relevant. If I got to the
>>>>>>>> source instance and pick a *category option combo*, in destination
>>>>>>>> instance for same *category option combo *the UID is different.
>>>>>>>>
>>>>>>>> For E.G.
>>>>>>>>
>>>>>>>> If I pick the dataset *Quarterly COIA Plus Dataset *
>>>>>>>>
>>>>>>>> In source instance, textbox in first row has id
>>>>>>>> *vIIFdYmaLk7-dCWAvZ8hcrs-val*
>>>>>>>> In destination instance, textbox in first row has id
>>>>>>>> *vIIFdYmaLk7-s1oqQs4sQhc-val*
>>>>>>>>
>>>>>>>> Which I think because *category option combo UID *is changed.
>>>>>>>>
>>>>>>>> Any clues what could be the reason for this?
>>>>>>>>
>>>>>>>> Thank You
>>>>>>>> Mritunjay Dubey
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jul 14, 2015 at 2:28 PM, Lars Helge Øverland <
>>>>>>>> larshelge@xxxxxxxxx> 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 <
>>>>>>>>> larshelge@xxxxxxxxx> 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 <
>>>>>>>>>> mritunjd@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
>>>>>>>>>>> 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 <https://www.dhis2.org>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Lars Helge Øverland
>>>>>>>>> Lead developer, DHIS 2
>>>>>>>>> University of Oslo
>>>>>>>>> Skype: larshelgeoverland
>>>>>>>>> http://www.dhis2.org <https://www.dhis2.org>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jason P. Pickering
>>>>>> email: jason.p.pickering@xxxxxxxxx
>>>>>> tel:+46764147049
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jason P. Pickering
>>>> email: jason.p.pickering@xxxxxxxxx
>>>> tel:+46764147049
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Alex Tumwesigye
>>
>> Technical Advisor - DHIS2 (Consultant),
>> Ministry of Health/AFENET
>> Kampala
>> Uganda
>>
>> IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya
>>
>> IT Specialist (Servers, Networks and Security, Health Information Systems
>> - DHIS2 ) & Solar Consultant
>>
>> +256 774149 775, + 256 759 800161
>>
>> "I don't want to be anything other than what I have been - one tree hill "
>>
>
>

Follow ups

References