Best practices for using "Back Compatible" option in Dataflows?

Akrem ABDELHAFIDH · 2025-07-21T13:51:33+00:00

There was an error rendering this rich post.

Hi everyone,

As part of a migration project from Board 10 to Board 14, I’m reviewing the use of the "Back Compatible" option in Dataflows.

I know this option should not be used with HBMP dataflows, but I’d like to go further and understand:

Are there any additional recommendations or best practices related to this option?
Is it safe to use it in cell-based Dataflows with IF() conditions?
What about arithmetic operations, like a - b or a + b?

Have you encountered any performance or functional issues when keeping this option enabled in such cases during migration?

Any advice or feedback from your experience would be greatly appreciated.

Thanks in advance!

Find more posts tagged with

Dataflow

Procedures

Configure

Accepted answers

Helmut Heimann

Hi @Akrem ABDELHAFIDH ,

Ultimately, you have to check all flows anyway to see whether they deliver the expected result. For the time being, I'd first let them work in compatibility mode, because you won't change all flows at once.

Then, I'd adjust them one by one—in the end, no flow should stay in compatibility mode.

Best,
Helmut

All comments

Helmut Heimann

Hi @Akrem ABDELHAFIDH ,

Then, I'd adjust them one by one—in the end, no flow should stay in compatibility mode.

Best,
Helmut

Akrem ABDELHAFIDH

Hi Helmut,

Thanks a lot for your feedback that makes perfect sense.

Appreciate your advice!