I want to create a confirmation page that displays the results of the data pulled and formats it in plain ol' html. No form (except maybe a button). It should be the simplest of tasks. I have yet to find any information how I can pull the results of my function, which populates form field views just fine, into a non-form html view. Have tried {var:.... {data:... - and every other thing I could think of. {var:function} gives me the full row in one big data-dump. The Details List set to display everything shows me a full array of my desired data. But there is nothing whatsoever documented in how to get this information into a basic HTML view where it looks readable. I call the function in my Event, and it works with forms. But...how am I supposed to import and use this data to plug it into regular html?
So you want... what exactly? Your data displayed in a table? Use a table, untick the "include form" toggle.
If you want to just display it normally, write your HTML and use {var:function.fieldname} where you want each data item.
Tried that. Doesn't work. Tried again just now. Tried just {var:function} and it gives me a data-dump of the fields in that record, but {var:function.field} produces nothing, even though the full dump showed data in that field.
Well crap - it works if I insert the model name - {var:fuction.model.field}
You know, I wasted many times more of my boss's money trying to figure this one simple little thing out than I paid to verify this software. Is a wiki too much to ask for? I got this because it was supposed to save me time from having to write my own component - but so far, it hasn't because there simply is no documentation.
There's a manual.
And If you use a debug action you can see the structure of the data.
Thanks. There is no Chronoconnectivity manual. What's in the Chronoforms manual only barely lightly touches on Chronoconnectivity, especially on the most rudimentary information like what this thread was about. If they are going to claim that Chronoforms manual also includes Chronoconnectivity, then they need to ditch the idea of having forms and connectivity being separate and just unite the codebase altogether. Too much redundancy.
