Skip to main content

Hello, i'my trying to compare efficiency of real-time project durations to theoric template durations. 

Projects are linked to tasks and tasks templates ;

-> total duration of a project = sum of the duration of each task

-> duration objective (efficiency) of a project = sum of the task duration objectives

In each project, Im trying to lookup the tasks theoric duration and sum it up to compare it to the actual project duration. 

I'm doing this this way : 
- I link projects to tasks

- Each task is linked to a ''task template''

- I look up the ''theoric duration'' of each task and Sum it up in rollup

The problem is that the sumup calculation is incorrect : see screenshot ->

- the first row, lookup values for theoric durations per project are as follow : 10, 10, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8, 8

=> And the calculated Sum is 20...

Does anyone encounters problem with this kind of sumup ?

Thanks for your help

 

What field type are you using for your durations? Duration? Number? Text? 


Maybe some filter is enabled? 
Scroll down here.


What field type are you using for your durations? Duration? Number? Text? 


Hello, thanks very much for your time and help. It's a lookup field that looks up a number field. 


Maybe some filter is enabled? 
Scroll down here.


Hello !

No its not the case, the result is the same with a formula SUM field. any other idea ?


Hello, thanks very much for your time and help. It's a lookup field that looks up a number field. 


Did you try using a rollup field on your project records to look at the numbers in your rollup field on your tasks records? That should work. 


Did you try using a rollup field on your project records to look at the numbers in your rollup field on your tasks records? That should work. 


Hello, not sure if i understood correctly, see screenshot of the rollup formatting : 

- Table projects (Routes) : rollup of the lookup fields of field ''objectifs temps' in table tasks (visits)

- Table tasks (visits) : lookup from a linked field (order_ID) to get the ''objectif temps''

 

 


"Objectif temps(min)/adresse" is a string, which may be the reason why the total fails.
If it is a number, it will be displayed on the right side of the cell.

How about changing the Lookup field to a rollup field and using the formula Value(values) to convert the values to a number field?


Try using a rollup instead of a lookup in your table tasks.


"Objectif temps(min)/adresse" is a string, which may be the reason why the total fails.
If it is a number, it will be displayed on the right side of the cell.

How about changing the Lookup field to a rollup field and using the formula Value(values) to convert the values to a number field?


Hello !

Thanks for the suggestion, just tried it but it returns ERROR message, see screenshot


Try using a rollup instead of a lookup in your table tasks.


 Tried so but still not working 😕😕 It seems the issues comes from the fact that the original field is a lookup (rollup from a lookup). Is it possible that a number data stored in a lookup field changes to a string ? How to change it back to a number ?


Oops, value(values) is an error.
Try sum(values)


 Tried so but still not working 😕😕 It seems the issues comes from the fact that the original field is a lookup (rollup from a lookup). Is it possible that a number data stored in a lookup field changes to a string ? How to change it back to a number ?


By using a rollup field instead of a lookup field for that original field. 


Oops, value(values) is an error.
Try sum(values)


Oh OK guys i think i almost got it ! it seems airtable rollup field switched to 0 the data when the lookup field has multiple values, see screenshot attached 

Lookup = 8, 8 ===> Rollup = 0
Lookup = 10 ====> Rollup = 10
Lookup = empty ====> Rollup = 0
Considering this, how do you thin i should solve this ?

@Databaser is right, the original Lookup field also needs to be a Rollup field.


Reply