See https://office.thinkwisesoftware.com/docs/docs/sf/subjects.html#tree for more information. Hi Mark,For me this link is invalid, it results in a 404 page. Can you please update it?Cheers
I believe to have found a way that suits our needs: let the function return a base64 encoded JSON message, instead of plain text.
@BasWesselink you can create the json but return it Table valued in stead of a scalar. That would return the json unescaped. Does the table-valued-function support nested data? Like { "orders": [ { "id": 1, "customer_id": 1, "order_date": "2023-06-31", "delivery_address": { "street_1": "street", "street_2": null }, "order_lines": [ { "id": 1, "product_id": 1, "price": 10.99 }, {
Hi Vincent, I had looked into that post before I made this one. The `$expand=` option was promissing, but further experimentation made clear that that can't be classified as low-code. It would be very complicated for an external party to write an interface to our API that way. And besides that, I feel I do not have control over the resulting JSON document. For example, when using `$expand=detail_..` I have no control over how it is put in the JSON message (can't use an ALIAS).The other option, as detailed in the blog post, can be thing to have a closer look at. But the fact that I then need to supply all features that come with OData, myself, makes it over complicated. Then, there is the table-valued-function. This lacks the ability to create a structured (nested) JSON message.Thinkwise almost does what I, and others need: return a JSON message that results from a query likeselect ... from ... join ... on ... for JSON auto instead of a string of characters that get escaped by so
Thank you for your extensive reply Mark. We may use that in a different issue, but for now it doesn't really fit the process(flow) I have in mind, as it adds an extra step in the process. I'm looking into an option where I use a hidden field to store the name of the field that has focus. And maintain that using the default 'trigger’ and @cursor_from_col_id/@cursor_to_col_id. Then the task (parameters) can use that hidden field, and no user input is needed.
... One step back, what are you trying to accomplish? Maybe there's an alternative solution possible. Hi Mark, I'm working on extracting data from (email-)messages, based on markers in the (body)text, and creating a to-do list item. It is possible to add and/or modify elements and markers, after a to-do list item has been made. So I want to be able to re-run the data extraction for one field (of choice) of one to-do list item. My idea is that by starting a (table) task, that 'knows’ what field (on screen) focus, by passing that field name as a parameter, I can determine the element by doing a lookup on [element].[mapped to ..], and be true to low-code ;) This way one task will suffice.I wouldn't want to have to make a task per field, or bothering the end-user with a dialogue window that needs user input, when the context is clear already. high-over data model:[element] → [marker settings] [element]name mapped to table mapped to column[marker settings]language BoL [CR/CR+LF/LF] start
This should also apply to `functions`
Running into the same issue here. Would like to have this request reconsidered.
Hi Erik,Maybe off topic, but is there any way to up-vote such ideas to get them a higher priority/on the backlog?Bas
Hi,Any chance the double click functionality will be available for card lists too? I would like to use it on a mobile device to start a task.
Does this idea need upvotes to get higher on the backlog? How are backlog items prioritized?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
