In the How to connect Tableau with 4D blog post, you learned how to create a web data connector (WDC) to request data from 4D and visualize it in Tableau Public.
Bonus: I’ll also show you how to debug your WDC in Tableau Public using Chrome. Let’s get started!
In 4D Webinar – How to Connect Tableau with 4D, William Taylor (Technical Account Manager, 4D US) gave an overview of the Tableau tool and how it could be used to visualize your 4D data. In this blog post, we’ll dig into the technical details to give you a deeper understanding of how it works. This will allow you to build, for example, a visual showing the highest invoice total with nothing more than 4D REST and Tableau!
By now you’re aware of the availability of ORDA classes. In this blog post, you’ll learn a few handy tips to get the most out of them!
In a previous blog post, we showed you that documentation for methods has returned in the Explorer. Want to take things even further and use them as documentation for your components? In this blog post, we’ll show you how!
One of the most interesting features delivered with 4D v18 was remote datastores. They opened a whole world of possibilities and in this blog post we’ll show you a practical use case:
In a previous blog post, we showed you how to get started with the 4D REST server. We walked you through different CRUD operations using Postman and pointed you to the full REST documentation. In this blog post, We’ll explain how sessions work in 4D. This understanding will ensure that you’ll be able to build a session-based authentication system using the 4D REST server.
Want to retrieve data that isn’t available via REST or Web Services? What if it’s only available on a website? The data is easy enough for a human to read, but reading HTML data with a programming language isn’t so simple. Some developers try to use Position and Substring, others try Regex, but it’s unpleasant and time-consuming. A very different approach is to convert the HTML into an object and get the data via object notation. Table rows are handled as collections and are easy to loop through!
This blog post describes how to use this approach and provides some handy tips.
4D provides a powerful REST server that enables direct access to data stored in your 4D databases. This makes it possible, for example, to build an API to use with a modern front-end technology (e.g., Angular, React, etc.). In this blog post, we’ll provide the first introduction to the 4D robust REST server. You’ll see how to configure it and test the create, retrieve, update, and delete (CRUD) operations using the API testing tool, Postman.
In a previous blog post, we introduced you to Git (a version control system) and Github (a cloud-based hosting service) and how you can share your 4D code with other developers. In this blog post, we’ll go a bit further by exploring some scenarios a developer may encounter, such as cloning a remote repository, ignoring already committed files, and solving merge conflicts.
With the introduction of project databases, we’ve also modified the interface of some 4D dialogs. In this blog post, we’ll present some of the changes we’ve made to the form editor.