Optimizing Ninox Workflow: Opening Database via URL with Parameters and QR Code Integration
I am writing to submit an important request to optimize our workflow, which I believe could also be useful to other users.
We are exploring the possibility of opening a Ninox database via an HTTP URL (e.g., app.ninox.com), passing parameters that allow us to access and pre-fill specific fields in the database. This functionality would significantly reduce the time our technicians spend inputting and updating information, improving overall efficiency.
Here is a detailed overview of our requirements:
Current Use Case:
- We have a database called "Store."
- Our goal is to automatically open the record associated with a specific machine by passing the serial number (SN) via URL.
- For example:
app.ninox.com?SN=25123456
In this case, SN represents the serial number of the machine to be edited.
Additional Details:
We have partially implemented a process where, by pressing a button on a Ninox form, the QR code is scanned, and the data is loaded.
However, we would like to go further. Ideally, when Ninox is opened via HTTP or the app, it would directly open the intervention request, selecting the relevant customer and machine.Ideally, the serial number could be stored in a global variable to pre-fill certain fields when the database is opened.
Challenges:
- Is there a way to pass parameters directly via URL to open and pre-fill fields in a Ninox database?
- Can this functionality be integrated with QR code scanning to open Ninox automatically after scanning?
- What solutions or third-party integrations could facilitate this process?
Desired Outcome:
To optimize the process for our technicians by allowing them to:
- Scan a QR code.
- Open Ninox via a URL link.
- Automatically access the record associated with the scanned serial number, with pre-filled fields for further input.
We understand that achieving this goal may require the use of external services or third-party integrations, and we are open to exploring these options. Additionally, if you have suggestions for alternative approaches or best practices for implementing this functionality, we would greatly appreciate your support.
Thank you for your assistance and for the continuous development of Ninox, which has proven to be an invaluable tool for our operations.
3 replies
-
I had a quick look at the URLs used by my databases and I think it's easy to parse
Each has the following elements concatenated together
Ninox app: app.ninox.com/#/
Team: teams/{team}/ find this using teamId() or looking at the URL
Database: database/{database}/ find this using databaseId() or looking at the URL
Module: module/{Table Nid}/ find this using tableId() or looking at the URL
View: view/{view}/ find this looking at the URL
Record: node/{Record Nid}/ find this using tableId() & Id or looking at the URL
Tab: tab/{tab} find this looking at the URL
You won't be able to use your machine serial number but substitute this with the record Id and you should be able to create QR codes for each machine.
Regards John
-
Another option is to use Zapier/Make to integrate between a web page or google form. Ninox's UI is not very good for touch, in fact it is horrible.
-
A Ninox partner built a WebApp for me that is used by my engineers to input data straight into my Ninox DB directly. It works a treat. It has login with password and can be used on a Laptop or Mobile.
Here is a sample screenshot:
If you want to get in touch with Scott to explore this option please let me know.
Content aside
- 2 days agoLast active
- 3Replies
- 44Views
-
4
Following