Day: November 27, 2017

ICYDK: I have been organizing my Human Services Data API (HSDA) specification work into separate microservices as part of version 1.0 for the API definition that cities and other organizations running 211 operations can pick and choose which aspects they want to run. One service I carved off of the move from version 1.0 to 1.1 of the specification was taxonomy, and how the human services are categories and organized. I saw there was more research to be done around 211 taxonomy, and I felt it had the potential to be a separate but supporting service to augment what Open Referral is already trying to do with the Human Services Data API (HSDA) specification.

The HSDA Taxonomy API specification provides a handful of API paths for creating, reading, updating, and deleting taxonomy used in any HSDA implementation. I have populated my demo API with the Open Eligibility taxonomy to help jumpstart folks, but any HSDA provider can populate with their own custom taxonomy, or another existing format. Then you can apply any taxonomy to any of the services stored within an HSDA database, and there is an API path for querying services by taxonomy. Next, I’ll make sure you can search by taxonomy, and see the taxonomy as part of the response body for all services returned across HSDA, HSDA Search, and HSDA Taxonomy. https://goo.gl/oKKmLP #DataIntegration #ML

Previous post https://blogs.sap.com/2017/10/26/using-a-third-party-library-with-sapui5-application-sap-hana-cloud-development-scenario-part-2/

Testing Odata Service :

In this part we have to validate our Odata service befor building the Front End application.

For this i will use Advanced Rest Client ( chrome Extension ). Create a new Request put the url to call Event Entity and added the “$top” parameter to the url to select just the first two events from the whole list.

If you are not familiar with Odata you can see this blog https://blogs.sap.com/2016/02/08/odata-everything-that-you-need-to-know-part-1/

This is the final set up we need to use GET operation and i added X-Csrf-Token = Fetch to use the result in the next operation

https://mdcpXXXXXXtrial.hanatrial.ondemand.com/Calendar/services/BookingEBC.xsodata/Events?$top=2 Events https://mdcpXXXXXXtrial.hanatrial.ondemand.com:443/Calendar/services/BookingEBC.xsodata/Events https://mdcpXXXXXXtrial.hanatrial.ondemand.com:443/Calendar/services/BookingEBC.xsodata/Events(‘00065ec7-9051-4798-a321-7dfc4eec09c9’) 00065ec7-9051-4798-a321-7dfc4eec09c9 Empty Task TEST 2017-05-11T09:00 2017-05-11T10:30 #77DD77 F 6f9137f3-092a-408b-9385-549ed7116ffb 2017 5 11 ONGABI https://mdcpXXXXXXtrial.hanatrial.ondemand.com:443/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’) 001e0529-8218-4a40-ad20-d7374516c38a Empty Task 2017-08-17T11:00 2017-08-17T12:30 #77DD77 F 6f9137f3-092a-408b-9385-549ed7116ffb 2017 8 17

If the call is executed correctly we should see a result similar to my XML. Pick one ID to check the GetDetail_Entity method by changing the URL.

https://mdcpXXXXXXtrial.hanatrial.ondemand.com/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’)?$format=json { “d”: { “__metadata”: { “type”: “Calendar.services.BookingEBC.EventsType”, “uri”: “https://mdcp601643trial.hanatrial.ondemand.com:443/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’)” }, “ID”: “001e0529-8218-4a40-ad20-d7374516c38a”, “TITLE”: “Empty Task”, “START_DATE”: “2017-08-17T11:00”, “END_DATE”: “2017-08-17T12:30”, “COLOR”: “#77DD77”, “STATUS”: “F”, “DESCRIPTION”: “6f9137f3-092a-408b-9385-549ed7116ffb”, “YEAR”: 2017, “MONTH”: 8, “DAY”: 17, “OWNERID”: “ ”, “CUST_COSTCENTER”: “ ”, “SREP_COSTCENTER”: “ ” } }

Back to Advanced Rest Client, copy the X-CSRF-TOKEN value and use it to send a PUT operation to modify the Event Content

Change the X-Csrf-Token value and the Request type and URL

https://mdcpXXXXXXtrial.hanatrial.ondemand.com/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’)

Change the body by putting the same JSON result from the GET operation request and modify some value and Execute the request.

Final JSON { “__metadata”: { “type”: “Calendar.services.BookingEBC.EventsType”, “uri”: “https://mdcpXXXXXXtrial.hanatrial.ondemand.com:443/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’)” }, “ID”: “001e0529-8218-4a40-ad20-d7374516c38a”, “TITLE”: “Empty Task Test”, “START_DATE”: “2017-08-17T11:00”, “END_DATE”: “2017-08-17T12:30”, “COLOR”: “#77DD77”, “STATUS”: “F”, “DESCRIPTION”: “6f9137f3-092a-408b-9385-549ed7116ffb”, “YEAR”: 2017, “MONTH”: 8, “DAY”: 17, “OWNERID”: “ONGABI”, “CUST_COSTCENTER”: “ ”, “SREP_COSTCENTER”: “ ” }

Change the operation from PUT to GET on the Advanced Rest and check the result

https://mdcpXXXXXXtrial.hanatrial.ondemand.com/Calendar/services/BookingEBC.xsodata/Events(‘001e0529-8218-4a40-ad20-d7374516c38a’)

The response should be like this.

Conslusion :

The Odata service is now ready and we can start the UI part in the next article. http://bit.ly/2i6Vtii #SAP #SAPCloud #AI