Yes, I agree with Markus,
Excel is good tool to do deep formula to calculate in data elements. And offline too.
Thanks Bob,
I have not established a preference here - your point on using CSV is a good one. CSV will probably be easier to “deserialize” in most cases. JSON or XML on the other hand, will probably be a little more robust to changes in the WebAPI output.
I like it. Excel is a good tool accessible to many people. I have been using an excel sheet to manage some data through the API, but the sheet I made contains some “hardcodings” that is made for my specific case. I have been thinking about making a generic version of my Excel, that can be used by anyone to post, put and maybe also get data through the API.
Best regards
Markus
p.s. I deleted the stackexchange question again, as the question and answer was generic Excel, and not so DHIS related. The link still works, but here is the code snippet.
It is possible to use Excel Macros to call the Web API. Posting to the API can be done like this:
Public Function postData(ByVal address As String, ByVal json As String, ByVal mode As String) If (mode = "Yes" Or mode = "Debug") Then On Error GoTo Errorhandler Dim objHTTP As New WinHttpRequest URL = address objHTTP.Open "POST", URL, False objHTTP.Option(WinHttpRequestOption_SslErrorIgnoreFlags) = 13056 objHTTP.setRequestHeader "Content-Type", "application/json" objHTTP.setRequestHeader "Authorization", "Basic " & EncodeBase64("admin:district") objHTTP.send json If (mode = "Debug") Then postData = objHTTP.ResponseText Else postData = objHTTP.statusText End If Else postData = mode End If Exit Function Errorhandler: postData = Err.Description End Function
For doing a GET, you should be able to just replace the “POST” with a “GET”, and send the request without the json.
Thanks for this information. That’s a really useful snippet for
anyone to get started who might want to do this. I have a quick
question and a comment/suggestion:
I can see from the link that you can indeed parse/serialize json
from VBA - I guess it would have been surprising if you couldn’t
Would you do this in preference to CSV?
On a a more general point, there has been interest in (and a long
historical relationship) between DHIS and Excel. Ranging from its
early origins in DHIS1.4 through to primitive efforts to populate
spreadsheet data using mydatamart. But the use cases from excel as
data collection instrument, through to excel for analysis (pivot
tables) and simple metadata management are very varied. It strikes me
that a library of DHIS2-web-api macros similar to those you presented
in your link would be hugely interesting to a lot of people. Have you
considered collecting/publishing such a thing?
You can’t use excel to get json data from dhis2 web api. At least not
directly.
You could possibly write an excel macro to “get” the data through the
web api (I am really not sure - it is far too many years since i wrote
an excel macro), but you are still left with the problem of consuming
what you have got (json) into cells in a spreadsheet.
I believe all (or certainly almost all) of the data which is available
as json is also available as csv. If you are looking at getting dhsi2
data into excel in general, I would look at csv rather than json if
you want to minimize the processing/transformation that would
otherwise have to happen in between getting the data and consuming it.
The excel thing is obviously something that we should address at some point. I have also made an unfinished attempt during the Ebola crisis. What I did was to provide a UI that allows users to upload excel file, do mapping between columns and data elements or attributes and finally upload the cell values.
I have not established a preference here - your point on using CSV is a good one. CSV will probably be easier to “deserialize” in most cases. JSON or XML on the other hand, will probably be a little more robust to changes in the WebAPI output.
I like it. Excel is a good tool accessible to many people. I have been using an excel sheet to manage some data through the API, but the sheet I made contains some “hardcodings” that is made for my specific case. I have been thinking about making a generic version of my Excel, that can be used by anyone to post, put and maybe also get data through the API.
Best regards
Markus
p.s. I deleted the stackexchange question again, as the question and answer was generic Excel, and not so DHIS related. The link still works, but here is the code snippet.
It is possible to use Excel Macros to call the Web API. Posting to the API can be done like this:
Public Function postData(ByVal address As String, ByVal json As String, ByVal mode As String) If (mode = "Yes" Or mode = "Debug") Then On Error GoTo Errorhandler Dim objHTTP As New WinHttpRequest URL = address objHTTP.Open "POST", URL, False objHTTP.Option(WinHttpRequestOption_SslErrorIgnoreFlags) = 13056 objHTTP.setRequestHeader "Content-Type", "application/json" objHTTP.setRequestHeader "Authorization", "Basic " & EncodeBase64("admin:district") objHTTP.send json If (mode = "Debug") Then postData = objHTTP.ResponseText Else postData = objHTTP.statusText End If Else postData = mode End If Exit Function Errorhandler: postData = Err.Description End Function
For doing a GET, you should be able to just replace the “POST” with a “GET”, and send the request without the json.
Thanks for this information. That’s a really useful snippet for
anyone to get started who might want to do this. I have a quick
question and a comment/suggestion:
I can see from the link that you can indeed parse/serialize json
from VBA - I guess it would have been surprising if you couldn’t
Would you do this in preference to CSV?
On a a more general point, there has been interest in (and a long
historical relationship) between DHIS and Excel. Ranging from its
early origins in DHIS1.4 through to primitive efforts to populate
spreadsheet data using mydatamart. But the use cases from excel as
data collection instrument, through to excel for analysis (pivot
tables) and simple metadata management are very varied. It strikes me
that a library of DHIS2-web-api macros similar to those you presented
in your link would be hugely interesting to a lot of people. Have you
considered collecting/publishing such a thing?
You can’t use excel to get json data from dhis2 web api. At least not
directly.
You could possibly write an excel macro to “get” the data through the
web api (I am really not sure - it is far too many years since i wrote
an excel macro), but you are still left with the problem of consuming
what you have got (json) into cells in a spreadsheet.
I believe all (or certainly almost all) of the data which is available
as json is also available as csv. If you are looking at getting dhsi2
data into excel in general, I would look at csv rather than json if
you want to minimize the processing/transformation that would
otherwise have to happen in between getting the data and consuming it.
Is anyone using Excel to create requirements and initial configuration for a DHIS2 instance? My team is trying to create one big spreadsheet that defines the data dictionary and, to the extent possible, the data model to set up a simple DHIS2 implementation. Worksheets would include indicators, data elements, categories, option sets, etc. … I know that we probably won’t be able to define everything in one spreadsheet (see the following except from Bob Jolliffe from another thread), but it sure would be helpful to use for requirements definition and for working with clients. And also to create templates for quick implementations to shorten the setup period.
I know that Juan has created some beautiful spreadsheets for user names and organizational units – has anyone else done this type of thing?
I have not established a preference here - your point on using CSV is a good one. CSV will probably be easier to “deserialize” in most cases. JSON or XML on the other hand, will probably be a little more robust to changes in the WebAPI output.
I like it. Excel is a good tool accessible to many people. I have been using an excel sheet to manage some data through the API, but the sheet I made contains some “hardcodings” that is made for my specific case. I have been thinking about making a generic version of my Excel, that can be used by anyone to post, put and maybe also get data through the API.
Best regards
Markus
p.s. I deleted the stackexchange question again, as the question and answer was generic Excel, and not so DHIS related. The link still works, but here is the code snippet.
It is possible to use Excel Macros to call the Web API. Posting to the API can be done like this:
Public Function postData(ByVal address As String, ByVal json As String, ByVal mode As String)
