Re: [Dhis2-devs] displayProperty NAME vs SHORTNAME in API

Thanks. On Tue, Mar 31, 2015 at 7:21 PM, Greg Rowles wrote: > Done: > https://blueprints.launchpad.net/dhis2/+spec/expanding-api-displayproperty > > > On Tue, Mar 31, 2015 at 4:57 PM, Lars Helge Øverland > wrote: > >> Hi Greg, >> >> yes we can add this long-term, feel free to write a blueprint.

Re: [Dhis2-devs] displayProperty NAME vs SHORTNAME in API

Done: https://blueprints.launchpad.net/dhis2/+spec/expanding-api-displayproperty On Tue, Mar 31, 2015 at 4:57 PM, Lars Helge Øverland wrote: > Hi Greg, > > yes we can add this long-term, feel free to write a blueprint. > > regards, > > Lars > > > On Thu, Mar 26, 2015 at 10:00 PM, Greg Rowles >

Re: [Dhis2-devs] displayProperty NAME vs SHORTNAME in API

Hi Greg, yes we can add this long-term, feel free to write a blueprint. regards, Lars On Thu, Mar 26, 2015 at 10:00 PM, Greg Rowles wrote: > Hi Devs > > Is there a chance the webAPI can support multiple parameters for > 'displayProperty' on different objects? > e.g. displayProperty=ou:NAME;d

[Dhis2-devs] displayProperty NAME vs SHORTNAME in API

Hi Devs Is there a chance the webAPI can support multiple parameters for 'displayProperty' on different objects? e.g. displayProperty=ou:NAME;de:SHORTNAME; We have terribly long data element and indicator names that are better suited as shortnames on reports but the ripple effect is our facility