Oh, and please make sure that you update the UIDs of these tables "default"
also. Since you might want to to those on import also. So delete the
duplicate default in those tables, but update the remaining default with
the duplicate uid (hope that makes sense).
--
Morten
On Wed, Jul 15, 2015 at 1:
Yeah, I think that should be ok, just make sure you have a backup ;-) When
it creates the default COC, it will also setup the tables around it,
probably you will see duplicate "default" names in those tables also.
--
Morten
On Wed, Jul 15, 2015 at 1:43 PM, Mritunjay Dubey
wrote:
> Hey Mortan,
>
Hey Mortan,
Thanx for your quick response. I tried deleting it from the table. But If I
see it has FK references to following table.
*categorycombos_optioncombos*
*categoryoptioncombos_categoryoptions*
*expressionoptioncombo*
So before deleting that category-option-combo I need to delete refer
Hi
You probably want to delete the "default" that was created during import, I
assume no FK is attached to it. After you have done this, you should be
able to change the UID of the other "default" COC to "dCWAvZ8hcrs".
This is the way we have solved it a few places (before it was fixed in the
cod
Hello all,
So as suggested I tried to update the "default" category-option-combo UID
to the UID of source instance. But it didn't work.
The reason was I already have a category-option-combo with same UID which
also has name "default". I think which came after import. So now it has two
"default" c
I meant 2.19
On Jul 14, 2015 2:47 PM, "Mritunjay Dubey"
wrote:
> Hey Knut,
>
> Upgrade means, Do I need to upgrade to 2.19, or somehow I can get a new
> revision of 2.16 only.
>
> Please let me know.
>
> Thank you
>
> On Tue, Jul 14, 2015 at 6:08 PM, Knut Staring wrote:
>
>> It has been fixed. J
Hey Knut,
Upgrade means, Do I need to upgrade to 2.19, or somehow I can get a new
revision of 2.16 only.
Please let me know.
Thank you
On Tue, Jul 14, 2015 at 6:08 PM, Knut Staring wrote:
> It has been fixed. Just upgrade.
> On Jul 14, 2015 2:33 PM, "Mritunjay Dubey"
> wrote:
>
>> Yes please
It has been fixed. Just upgrade.
On Jul 14, 2015 2:33 PM, "Mritunjay Dubey"
wrote:
> 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 U
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
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
wrote:
> Dear Dubey,
>
> Jason is right.
>
> I have had trouble before with a similar issue doing imports.
> One thing I keep in mind whe
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, f
That would explain it, as 2.16 is a year old now...
On Tue, Jul 14, 2015 at 12:32 PM, Mritunjay Dubey wrote:
> Hey Jason,
>
> We are using DHIS 2.16 at both instances.
> The build rev for source instance is *16594* and for destination instance
> it is *16598*.
>
> Let me know if it is fixed.
> T
Hey Jason,
We are using DHIS 2.16 at both instances.
The build rev for source instance is *16594* and for destination instance
it is *16598*.
Let me know if it is fixed.
Thank you
On Tue, Jul 14, 2015 at 3:49 PM, Morten Olav Hansen
wrote:
> Could you also please provide your DHIS 2 version a
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.picker...@gmail.com> wrote:
> In this case, you should probably alter the "default" c
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 = 'X' where
categoryoptioncomboid = (SELECT categoryoptioncomboid from
_
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 syn
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 wrote:
>
> --
-- Forwarded message --
From: Mritunjay Dubey
Date: Tue, Jul 14, 2015 at 2:58 PM
Subject: Re: [Dhis2-devs] Deployable war for previous builds
To: Lars Helge Øverland
Just adding to that
We had selected every metadata other than *Validation-criteria & Report
Table.*
And while i
18 matches
Mail list logo
