dhis2-devs team mailing list archive

["Tran Chau (HISP Vietnam)" <tran.hispvietnam@xxxxxxxxx>]

Thank Greg,

I tried creating a formula as your simple formula and chose the Task
strategy as 6 months, the data is generated and saved ok for 6 months in my
side. Please see the attachment snapshots.
I guess maybe data in your database got some issues.

Besides, when Task strategy is changedd from  "12 months" to "6 months", we
have to click *Stop *button and *Start *button before clicking on
*Execute *button.
If not, the system will run with the old Task strategy which we did set
when we start *Schedule automated aggregation* before.

.................................
Best regards,
Tran Chau


On Thu, Feb 26, 2015 at 10:31 PM, Greg Rowles <greg.rowles@xxxxxxxxx> wrote:

> Hi Tran
>
> The schedule was changed from "12 months" to "6 months" but we are testing
> aggregation outcomes using the "Execute" command (most of the time it just
> hangs with "504 (Gateway Time-out)" and we also noticed the same for
> "Manual Aggregation", preview & save options). Our basic formulas use
> [Visited selected program stage] criteria while we have a set using more
> complex DateDiff() formulas. We know we have tracker data starting in
> Aug-2014 up till a few minutes ago:
>
> [image: Inline image 1]
>
>
> Complex Query:
>
> [image: Inline image 2]
>
> Basic Query:
>
> [image: Inline image 3]
>
>
> I hope this is what you were asking for...?
>
> Best,
> Greg
>
>
> On Thu, Feb 26, 2015 at 3:05 PM, Tran Chau (HISP Vietnam) <
> tran.hispvietnam@xxxxxxxxx> wrote:
>
>> Hi Greg,
>>
>> Can you give me more information about snapshots, your formulas, your
>> event cases, what the *Task strategy* is selected in *Schedule automated
>> aggregation* .... ?
>>
>> ..................................
>> Best regards,
>> Tran Chau
>>
>>
>>
>> On Thu, Feb 26, 2015 at 5:26 AM, Greg Rowles <greg.rowles@xxxxxxxxx>
>> wrote:
>>
>>> Hi Devs
>>>
>>> We've noticed our Aggregation-Queries are only loading values for the
>>> last month regardless of the selected time frame.
>>>
>>> Is there a known bug or known cause for this problem? Perhaps its a
>>> data-quality issue (we're still refining our data quality kinks, i.e. there
>>> may be programstageinstance.executiondate dates that violate expected
>>> values, e.g. date value "0013-02-13" and "0022-02-06" is present). Is
>>> this the likely cause? We cannot aggregate data before 24 Jan 2015...
>>>
>>> Greg
>>>
>>> --
>>> *Health Information Systems Program - South Africa*
>>> *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - -
>>> - - *
>>> Mobile  :    073 246 2992
>>> Landline:   021 554 3130
>>> Fax:          086 733 8432
>>> Skype:      gregory_rowles
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
> --
> *Health Information Systems Program - South Africa*
> *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - - -
> - *
> Mobile  :    073 246 2992
> Landline:   021 554 3130
> Fax:          086 733 8432
> Skype:      gregory_rowles
>

Attachment: [1] Aggregate Query Builder.jpg
Description: JPEG image

Attachment: [2.1] tracker data.jpg
Description: JPEG image

Attachment: [2.2] tracker data.jpg
Description: JPEG image

Attachment: [3] result afer runing .jpg
Description: JPEG image