OK thanks.  I suppose the question is also related to the earlier
discussion today about harmonising uuids, at least between systems in
a particular universe, so that whatever grammar which emerges for
defining a report would make sense between those different systems.

On 2 April 2012 16:46, Michael Seaton <[email protected]> wrote:
> Hi Bob,
>
> It is not a silly question.  It is planned, but currently not possible.
>  I've been putting it off a bit since we are considering re-writing the
> means by which reporting definitions are stored in the database, and because
> many of our users interact with the reporting module via the API through
> module.  I agree that this is a pretty important feature to have for anyone
> defining their cohort queries, indicators, and reports, exclusively via the
> UI.
>
> Mike
>
>
>
>
> On 04/02/2012 11:07 AM, Bob Jolliffe wrote:
>>
>> Apologies if this is a silly question.  Setting up reports with cohort
>> indicators, cohort queries etc can be quite an involved process.  Is
>> there a straightforward way to share these reports between systems?
>> Is it just a particular subset of metadata import/export
>> functionality?
>>
>> Regards
>> Bob
>>
>> _________________________________________
>>
>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
>> [email protected] with "SIGNOFF openmrs-devel-l" in the  body (not
>> the subject) of your e-mail.
>>
>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
>
>
> _________________________________________
>
> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
> [email protected] with "SIGNOFF openmrs-devel-l" in the  body (not
> the subject) of your e-mail.
>
> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to