Any reason you simply do not use the UID of the sql view instead?
On Wed, Jul 8, 2015, 21:18 Alan Hill ah...@2paths.com wrote:
Fixed: needed to set
URIEncoding=UTF-8
in tomcat's server.xml file.
On Wed, Jul 8, 2015 at 11:49 AM, Alan Hill ah...@2paths.com wrote:
Hi there
We have a
Only that we are not creating the view with a known UID.
On Wed, Jul 8, 2015 at 12:38 PM, Jason Pickering
jason.p.picker...@gmail.com wrote:
Any reason you simply do not use the UID of the sql view instead?
On Wed, Jul 8, 2015, 21:18 Alan Hill ah...@2paths.com wrote:
Fixed: needed to set
Ok, bit you could create the view with a known UID by transmitting this
through the API , and even if you changed the name, the UID would never
change. Would seem to be simpler and more reliable.
Regards,
Jason
On Wed, Jul 8, 2015, 21:45 Alan Hill ah...@2paths.com wrote:
Only that we are not
Thanks Jason.
We have just created the views through the UI but realise that we should
probably do it through the API.
Thanks for your help.
Regards
Alan
On Wed, Jul 8, 2015 at 12:55 PM, Jason Pickering
jason.p.picker...@gmail.com wrote:
Ok, bit you could create the view with a known UID
Hi there
We have a number of sqlViews in our DHIS2 instance with foreign characters
e.g.
Programmes avec les données
We are having trouble retrieving these by name through the API e.g.
/api/sqlViews.json?filter=name:eq:Programmes%20avec%20les%20données
However, the following does
Fixed: needed to set
URIEncoding=UTF-8
in tomcat's server.xml file.
On Wed, Jul 8, 2015 at 11:49 AM, Alan Hill ah...@2paths.com wrote:
Hi there
We have a number of sqlViews in our DHIS2 instance with foreign characters
e.g.
Programmes avec les données
We are having trouble
6 matches
Mail list logo
