NEXEL + CROSSVIEW + COUNTIF not working?

Carlos Eduardo Meneses Maran · 2025-01-22T16:07:27+00:00

There was an error rendering this rich post.

Hi all,

On the row "0" of the second layout, I tried a deepest entity formula Nexel: =COUNTIF([#Data;@a;*;Range.Vertical],"=A") but can't make it count how many "A" lies on the first layout.

I've also tried:

=COUNTIF([#Data;@a;*;Range.Vertical],"A")

=COUNTIF([#Data;@a;*;*;Range.Vertical],"A")

And many others, but can't make it works

Can you see a solution?

Find more posts tagged with

Dataview

Algorithm

Accepted answers

All comments

Helmut Heimann

Hi @Carlos Eduardo Meneses Maran ,

if you try to run that calculation in a single dataview (i.e. without the crossview) — what results do you get then?

Best,
Helmut

Bettina Clausen

Please note that the Screen must be saved before using the CrossView feature. It won't show the result in the Nexel configurator.

Carlos Eduardo Meneses Maran

Hi @Helmut Heimann, thank you very much for your answer,

Without the crossview it works, look at this:

It works independently writing "=A" or "A" as should be.

So why the aim of using crossview: because we need to perform a bi-dimensional counting on-the-fly and present it in the form of a table.

For my try using crossview, I was wondering if I was misleading the correct reference to rows, columns or ranges because the statistical counting works on different entities.

Thank you @Bettina Clausen, I didn't know that was necessary when using crossview, however, instinctively I always saved and refresh to assess the result.

Helmut Heimann

Hi @Carlos Eduardo Meneses Maran ,

I've rebuilt your example and concluded that the COUNTIF does not work as expected. Unfortunately, it only calculates correctly if the referred block is in the same layout.

I'd suggest you open a ticket with our support—and please keep us posted.

Best,
Helmut

Carlos Eduardo Meneses Maran

Thank you, @Helmut Heimann, I'll do it like that.

Jason Febo

Nexel and Crossview are areas that usability has a lot of room to be improved. There really isn't any error handling or indication of where things are going wrong. If everything is 100% perfect, you can get the desired results. If not, things fail silently, or the whole layout or screen goes "OOPS ⚆_⚆".