Skip to content
Become a partner
Data Apps · ProAdmin's applications

Applications for your data. One table, every view.

With Data Apps, a company keeps its data in shared tables, with rights, and looks at it however it needs: as a list, a kanban board, a calendar, on a map, as a spreadsheet or a pivot table. An application assembles these views into screens. The data stays with the company, on its ODESA server.

Shared tables17 viewsVersions and rightsNo developer needed
Offer Data Apps to your clients See all the views
The principle

Data first, screens second

The data does not live in the application: it lives in “My data”, and each application is just one way of showing it. Two applications can therefore work on the same tables.

Spaces and tables

  • Spaces organise tables in a tree, like folders.
  • A table is a list of records: clients, invoices, sites.
  • Rights are granted on a space or a table: read, write, manage.

Typed fields

  • Text, number, amount, date, choice, e-mail, phone, file, image, colour…
  • A calculated field follows a formula, recalculated on every write.
  • Personal data is identified and hidden from anyone not allowed to see it.

Links between tables

  • A link field connects an invoice to its client, a site to its crew.
  • Sub-items total the linked records: count, sum, average.
  • A deletion is blocked, cascaded or cleared, according to the chosen rule.
Field types
  • Text
  • Long text
  • Markdown
  • Number
  • Integer
  • Amount
  • Percentage
  • Rating
  • Date
  • Date and time
  • Time
  • Yes / no
  • Choice
  • Multiple choice
  • E-mail
  • Phone
  • Web link
  • Country
  • Colour
  • Person
  • User
  • Link to a table
  • File
  • Image
  • Auto number
  • Created on / by
  • Modified on / by
  • Sub-items
The application

An application is a tree of screens

The designer assembles folders, lists and views. Each screen shows a table with the chosen view, and what each person is allowed to do there.

  1. 1

    Create the tables

    Fields, links, choices. Or import a CSV file, without overwriting what is already there.

  2. 2

    Choose the views

    For each table, as many views as needed: kanban, calendar, map, spreadsheet…

  3. 3

    Build the application

    Screens, forms, buttons and the Logic that automates.

  4. 4

    Approve and publish

    The draft is approved, then published; every version is kept, and you can roll back in one step.

The views

17 ways to look at the same data

A view copies nothing: it shows the table differently. You switch in one click, and each one keeps the person's rights.

List and organise

TableThe table, record by recordSee the view KanbanColumns, and cards you dragSee the view GalleryCards with their imageSee the view

Time

CalendarRecords laid out on the monthSee the view TimelineThe schedule as barsSee the view ProPlanningThe team's full calendarSee the view

Analyse

Pivot tableTotals by row and by columnSee the view ChartBars, lines, ringsSee the view WidgetA dashboard that takes actionSee the view SpreadsheetFormulas on your recordsSee the view

Documents and places

FilesThe table's document managementSee the view MapRecords on a mapSee the view

Compare

ReconciliationTwo tables side by sideSee the view 3-way matchingInvoice, order, receiptSee the view

Business views

ProInvoiceQuotes, invoices, credit notesSee the view ProMailThe team's mailboxSee the view ProContactThe address bookSee the view
In demo

Other views are already running on the demo instance: the Binder, a document processing desk, and the ProShare explorer for server folders. They will reach production later.

Logic

An application that acts, not just a screen

Logic means small scripts attached to the application. A click, an event or the server starts them: they check, calculate, write and notify. The language comes down to simple commands, like spreadsheet formulas.

A button

In a record's form, above a view, on each record in the table or on the ticked records. It can open a form before acting.

Approve the quote · Send the reminder

An event

A new record, a changed field, before or after saving, before a deletion, a card moved on the kanban board. Logic can refuse the operation, with a message.

No approval without an amount

The server

The ODESA workstation runs Logic even with the application closed: a file dropped in, a time of day, a due date, an e-mail received.

Every morning at 8 am · 3 days before the due date

What it can do

  • Check and refuse
  • Calculate
  • Search the tables
  • Create and edit records
  • Ask a question in a form
  • Notify the team
  • Send an e-mail
  • Reply to and file mail
  • Generate a document
  • Organise files
  • Ask an AI

96 documented commands, each with an example.

Read the documentation
Demo exampleThe “Send the reminder” button, visible when a reminder is due on the invoice
SendMail(@destinataire, "Reminder for invoice " & $ref, Render(@modele_relance))SetField("statut", "Reminded")Notify("Reminder sent to " & @destinataire)

What makes it reliable

  • An editor that flags errors as you type, with completion and help for every command.
  • A dry run: you see what the script would write, without writing anything.
  • An application with faulty Logic cannot be published; the draft is kept.
  • It works with the person's rights, and the workstation with its own rights.
  • The number of commands and writes is capped: a loop cannot run away.
  • An execution log, switchable application by application, keeps every run.

Events fire inside the application. A record that is imported or written by an AI assistant takes another path: to process it, you rely on the ODESA workstation.

Under control

Rights, versions, and an AI that respects them

An application never sees more than the person using it: the tables' rights always apply. Other people's changes arrive live, and every published version stays available.

  • Rights are granted to people, groups or roles.
  • Every published version is kept: you can roll back in one step.
  • A contractor can design an application without ever seeing a value.
Rights

On the tables for the data, on the application for using or designing it.

Versions

A draft, an approval, a publication: you can roll back in one step.

The AI assistant

Through the MCP connector, an assistant such as Claude builds or uses an application, with the person's rights.

For you, the reseller

How to offer it to your clients

Who for

  • SMEs that live in Excel files sent by e-mail.
  • Companies with an Access database or a small in-house program to replace.
  • Teams that want a shared tool, with no development.

What you sell

  • Converting the client's files into tables, with their links and rights.
  • Applications built with each team: views, forms, Logic.
  • Improvements, version after version, without breaking what works.

Lines that work

Your Excel files become real applications.
One table, and every way to look at it.
No developer, and no copy of the data.
Partner programme

Build your clients' applications.

You keep the relationship and the advice; ProSuite provides ProAdmin, ODESA and the updates.

Become a partner The partner programme