-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested relations in Formula columns #14591
Comments
i just tested it with version 2.32.5 and situation is same |
Hey @lldev0. The correct syntax here is the real column name Static formula column values are actually saved into the table. Try recreating this with static formula columns and see if that works. In my testing locally I can recreate this and get it to work by using static formula columns. |
could you please confirm if "static" formulas are working also if we are using MySQL or PostgreSQL database as a source ? because I see this option in your documentation https://docs.budibase.com/docs/formula but do not see it in our deployed app |
Ah apologies - didn't realise it was MySQL. You're right, static formulas aren't available on external datasource so please ignore my answer! Another workaround is probably just include the nested formula inside your other table formula. So instead of using So I'm sorry but I don't think this is possible at the moment. Sounds like a valid feature request though! |
Checklist
Hosting
Describe the bug
I have a 3 tables with 1:n relationship as per this model:
First have only defined relationship to second table and is working fine:
Second table is with formula generated column named landscape_name {{ asset.0.asset_name }} - {{ landscape_type }} as a display column and also working fine:
Third table also have formula generated display column named environment_name, but this one is not getting correct display column name from second table, tried 2 different approaches:
{{ landscape.0.landscape_name }} - {{ environment_type }} - {{ environment_region }}
and
{{ landscape.0.primaryDisplay }} - {{ environment_type }} - {{ environment_region }}
Formula generated column environment_name should look like this:
%asset_name% - %landscape_type% - %environment_type% - %environment_region%
Application 1 - prod - production - germany
Application 1 - prod - production - france
Application 1 - prod - preproduction - germany
Application 1 - nonprod - uat - usa
Application 1 - nonprod - dev - usa
etc...
So probably there is a bug which is preventing using nested formula columns. I tried this with MySQL and PostgreSQL database, same behaviour
Expected behavior
Formula generated column in third table should pick correct display name from second table
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: