This should get you started:
define temp-table tt serialize-name 'keyboard'
field ckey_label as char serialize-name 'key-label' xml-node-type 'attribute'
field ckey_value as char serialize-name 'key-value' xml-node-type 'attribute'
field special-lKey as char
field cimage_up...
Once the temp-table has been temp-table-prepared you can no longer modify it. You can copy-temp-table to a new temp-table and add your field to the copy.
You just need to get rid of the intermediate variables b1 and b2 since b2 is always evaluated even when it's value is irrelevant based on b1.
function bitOR returns integer (input X as integer, input Y as integer):
define variable n as integer no-undo.
define variable Z as integer...
1. please put code inside [ code ] tags to make it legible
2. when you have a problem and would like others to help you with it, it helps if you reduce the problem to the smallest version of the problem. Showing how you assign NINE fields with all sorts of crap does not help.
What you need is...
Not that I can share.
I can share that we started by reducing an xlsx to a bare minimum (there is a lot of fluff in an empty worksheet) and then building it up with our content. It's a lot more fun than reading through pages and pages of specifications.
We use option 3
Create an xlsx file (is multiple xml files created using sax-writer, which are then zipped as xlsx) - fetching simple data (1 table), creating report and creating excel file takes less than 1 second (640 records, approx 20 columns)
If your backend service can use .Net and if it can create an ABL window and if you can hoist this in a .Net window, then you may be able to use the CopyFromScreen method.
If you view the documentation on the RequestBuilder you can see what the Put method needs:
OpenEdge.Net.HTTP.RequestBuilder Put (character, Object)
OpenEdge.Net.HTTP.RequestBuilder Put (URI, Object)
OpenEdge.Net.HTTP.RequestBuilder Put (URI, Object, character)
So you always need to...
The question title:
But, using your example and manually creating the child records based on the extent, may be easier but also more error prone, than digging into how JsonObject and JsonArray work.
Of course it fails, that's why you need to disect the json yourself using JsonObject and JsonArray - look these classes up on docs.progress.com
google site:docs.progress.com JsonObject
google site:docs.progress.com JsonArray
If you just need to know which tables are hit, to get insight into the black box your application may be, you can monitor this using _TableStat or _UserTableStat
To not reinvent the wheel, you could look at - the free version of - ProTop.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.