E
egarcia
Guest
Hello, > Question 1: Is there any special trick to getting the jsdo to put the data into a property named like your temp > table? No, there is no special trick. It should work just fine with BEs and catalog files generated with PDSOE. The BEs use a prescriptive approach. > Question 2: What in the world is going on here? Why would a foreach return the entire dataset? Why would > the resulting JSRecord object not have fields defined in it like the documentation says it does? Could you share the signature of your READ method and the corresponding catalog .json file? What version of the JSDO are you using? Where are you downloading the JSDO from? Are you downloading it from npm ( www.npmjs.com/.../jsdo-core )? Older versions of the JSDO used jQuery Promises and the promises used a signature like this "(jsdo, success, request)". Recent version of the JSDO use JS (ES6) Promises and the promises use (object) as the signature. (The new version has a mode that allows usage of jQuery Promises if desired.) > Does anyone have a really simple example of using a jsdo with plain old JavaScript to access a BE's > methods? Maybe a tutorial out there that doesn't involve mobile development or Kendo? Here are some examples: - oemobiledemo.progress.com/.../example001.html (JavaScript Promises) - oemobiledemo.progress.com/.../example013.html (jQuery Promises) The wiki in GitHub also has an example: - github.com/.../Using-the-JSDO-component-with-plain-HTML-and-JavaScript I hope this helps.
Continue reading...
Continue reading...