[progress Communities] [progress Openedge Abl] Forum Post: How To Connect To A Business...

  • Thread starter Thread starter tinkerfixergeek
  • Start date Start date
Status
Not open for further replies.
T

tinkerfixergeek

Guest
Hello, I'm having some trouble understanding how to go about connecting to a remote data source that would be a business entity created in PDSOE via my JavaScript code. For example purposes, I am using the Sports database. I have created a business entity in DevStudio from the Employee table. I exposed the service to my local PASOE instance and have no issues seeing the service or the data via a browser. Opening KUIB, I created a basic test app and can see the data using a basic grid view without issue as well. The problem I am having is beyond this basic usage. I have created a blank view with a couple of custom HTML elements that I can work with in the Controller.Public.js file and I am trying to figure out how to properly write the calls to talk to my business entities. For example, trying to get just a basic KendoDropDownList to work: $("#employees").kendoDropDownList({ dataTextField: "FirstName", dataValueField: "EmpNum", dataSource: { transport: { read: { dataType: "json", url: " localhost:8810/.../beEmployee", } } } }); Using a business entity that contains data that looks like: "dsEmployee": { "prods:hasChanges": true, "ttEmployee": [ { "EmpNum": 1, "LastName": "Koberlein", "FirstName": "Kelly" } ], "prods:before": {} } I think my issue is in a misunderstanding of what the type of data is, but there are not many examples currently of connecting to this kind of entity (JSDO?). The current Kendo examples all seem to be using JSONP or ODATA types. I can get custom elements to work with locally created data sources and have seen some examples that looked like they were converting the incoming data into a local source. Is that what should be done, and how would I do that if so? I've also seen examples where a schema and model are used but am unsure of how that would look either. James

Continue reading...
 
Status
Not open for further replies.
Back
Top