Recap DB

Max.. Is this via a local application or the Ninox Cloud?   If the later, take a look at the REST/API.. You can get listing of database tables / fields.. etc.. 

https://ninoxdb.de/en/manual/api/rest

many thanks, I'll try..

You most likely will want to a test with ninoxApp() - returns one of "mac" | "ipad" | "iphone" | "web", identifying the type of app

Ooops.. wrong thread...   For the DB Recap... I checked out the REST/API.. Tables will give you the table structrure .. but not all the nice things we see via the application... the the formulas / values.. triggers etc... That would be a GREAT enhancement. 

yes especially for the big structures, many thanks

I am working on a quick "Document" database.. I have it to the table level.. I need to work through all the various permutations of the fields.  Once complete.. I will post in the Webinar Team and notify Support to review. 

great, I'm looking forward.

Still thanks

I emailed you a sample database to your email displayed via your profile.   Post here if you do not receive it.  Once YOU add a nice report.. we can share with Support and they can post in the Webinar as a solution.   I guess another enahncement would be a check box to "capture all" at the Database level.. for simplicity .. it is manual.. :) 

I have seen numerous people ask how they can document the database...   Before we invest more effort.. I am submitting an enhancement request such that the REST/API return ALL attributes we see via the application UI.. ;)

Happy NinoxING.. 

I received the email, tomorrow I’ll take it a look and in this week end I’ll try to add the report.

ciao

I received the email, tomorrow I’ll take it a look and in this week end I’ll try to add the report.

ciao

I ended up working backwards and making a software design document after I had my DB up and running.

You can get a lot of info with the REST API, but not everything.

Part of it was just taking screen shots to see the UI, and the "Edit Fields" screen.

Lots documenting all of the formulas and scripts with copy/paste.

Now that I have a better understanding of how Ninox works and what it can do, I try to document DBs beforehand, then as I make changes.

I totally agree with blackie.. Nothing is better than keeping documentation current.  Still, this was a fun exercise to learn a bit more about the API.     I posted 36_Document_Database_Structure to the Webinar EN 2018 Team.  The API Key field is set to READ ONLY and there is a header warning folks NOT to put their private API Key in there..   They should download it first .. then play with it. 

Next task.. figure out a more elegant way to display json results in a "view".  Views seem to want "records" .. and "response.result" seems to be an object .. not a record.. but I did not spend more than a few minutes thinking about it. :) 

You might have already come up with a solution, but this is a possible solution (Not tested in this specific case). Create a table specifically for global/persistent/placeholder variables and store the response.result in a text field or multi line text field.

@Mconneen, I have a tendency to overthink things. If all you’re wanting to is display the json result, wouldn’t a formula field work?

@SlowWagon... I already have a "Configuration" table that I hide and store configuration data.. when necessary. 

Oh.. and "Over thinking things"... I like to call that "I go around the block to go next door".. :)