Similar to the examples of Strapi:
Imagine I have either a table or view in NocoDB that represents a list of restaurants.
The restaurant may have fields like:
- Address (some sort of geocoding that allows a map to be displayed)
- Menu (some link to a table of orderable dishes)
- Open hours (either a text with the full definition encoded (like in JSON), either a link to a table with rows that represents opening slots)
I want a No-Coding way to “display” the data inside a system that is not NocoDB itself.
For example, I was thinking Wordpress. Make some sort of page that receives some sort of parameter that displays one entry in NocoDB.
For example https://example.com/restaurant/?restaurantId=1234
What’s the easiest way to make an external display of the data in the NocoDB with ZERO-CODING?
Do you intend just to get API response from the such URL ? or do you like us to apply the said fields / filters for the NocoDB view ?
Thanks for considering the question.
Answering you: I’m not really clear on what I want. As I’m new to nocoDB, I am currently more trying to discover what’s possible to extract the maximum efficiency when designing (later on) mechanisms to integrate nocoDB with our systems.
Let me put a real example in my company: We are currently using Hubspot as a CRM. We mainly have:
- Contacts (represents a person that is either a customer or a potential one)
- Deals (represents the process for a potential purchase).
- 1 Contact has 0 to n Deals.
- Each Contact has a history of events:
- Annotations general to the contact, logged calls not related to any specific deal, etc.
- Each Deal has a history of events:
- Annotations specific to this deal, logged calls regarding this deal.
Each entity has some properties:
- Each contact has properties like verified or not, etc.
- Each deal has properties like negotiation stage, potential amount, etc.
Appart from the Hubspot CRM we have an “agent panel” where our workers may access multiple information.
I was thinking to move all or part of the data from Hubspot to nocoDB and integrate in the agent panel some views that allow them navigate via the information.
- List of contacts that I should attend today (for example those with open deals that have tasks pending to be completed), and able to navigate to the page of a specific contact.
- List of deals, and able to navigat to the page of a specific deal.
- Specific contact record (full-page contact display with all the relevant info, including the list of open and past deals for that person, and able to navigate to the deals)
- Specific deal record (full-page deal display with all the relevant info, like the logged calls, annotations, internal notes, sent quotations, etc.)
a) If all the interface is read-only I already win with respect what I currently have.
b) If I can take advantage of filtering and sorting, even better than a).
c) If I can set buttons in there to interact with the data, better even (for example when displaying a contact, a button to set a “verified” flag in the database) that’s better than b).
d) If that in fact records events and those events get projected into the nocoDB (being nocoDB the read-side of a CQRS system) even better than c).
I currently know how to do this with coding all that by myself. I usually have our applications in PHP and symfony and that’s perfectly fine.
The question in fact is: Might I do all this with a no-coding approach? For example in a wordpress (or even in any other no-coding platform).
This would open the potentiality to make things happen much faster because non-coders (ie: marketing people) could prepare the applications by themselves.
The goal of my question was to know how people are currently handling those types of no-coding full-stack systems in real situations when using nocoDB as the data-source.
Thank you so much for such a detailed explanation. You really know what you need
I have created a feature request for this. From my understanding the params level feature is already available at API level - its the matter of bringing to views level.
I would love to learn more about this detailed usecase above - if you could please book a time for us to chat that would be really helpful.