Limitations of Query Apps

Dear all,

this is my first post. Thanks for this great forum. I appreciate any help.

I was wondering why query apps cannot search all column types (for example “long text”) and how to overcome this limitation.

I’d be happy to see this thread developing into a collection of other limitations of Query Apps.


The query app is subject to pretty much the same limitations as the base editor is. As a rule, if a column can be filtered (not all can), the column can be queried in the query app. Exceptions apply.

The long text column is such an exception. Why? Keep in mind, the character limit for a single cell is 100.000. This is a lot of text! Filtering over such a column may be very heavy. For this reason, the available filter operands for the long text column are only “is empty” and “is not empty”. And you cannot sort by the contents of the long text column. In the query app, the long text column cannot be added as a query field. Sorry.

1 Like

Another exception: Columns from linked tables and columns with “lookup” link formula CANNOT be queried but CAN be filtered.

It would be great if those columns can be queried. Otherwise, I need to pack everything in one single table, and common datasets are not of much use.

my use case:
I want to build an employees directory with their job descriptions.
with 3 groups:

  1. a group for the executive board: providing the list of departments as CDS;
  2. a group for the HR department with list of employees shared as CDS (without salary column);
  3. a group for all employees, with a base called job description, which combines the two CDS.

The advantage: the list of departments is managed in one central place, and thus changes only need to be made there.

At the moment, due to the query restrictions, I made one table with departments as “single select column”. The problem: when I will create another table with a departments column, I need to define them again inside the table.

@rdb : do you have any plans to address these limitations on your roadmap?
thanks for your help!

I just came across another limitation :thinking:

Cascaded single select columns work perfectly fine in tables and forms.
However in Query Apps, no matter which parent option is chosen, all child options from all parent options are shown.
This can be very confusing and lead to meaningless queries.

Hello Gregor,
please excuse the late feedback.

I am just trying to understand your use case:

What exactly do you mean by three groups?
Are you talking about a base with three different tables that are filled by CDS?

You are using the app “Data query” to search for e.g. employees?

Could you please summarize the case again and maybe send me screenshots, so I can understand the problems you encountered?

Thanks in advance and best regards