Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi there
So I basically have this project table, which has Project ID plus 100 columns, among them beginning and end date columns. The code below, counts the dates in the calendar that are between the beginning and and ending date for each project.
What I do not understand, is why do I need a Calculate around another calculate. It is my understanding that Calculate by itself does context transition, so wouldnt the first (inner one) calculate be sufficient to filter the beginning and ending date row by row? If I didnt place the second calculate the result would be blank in all rows.
Translation from the code: "Calendario ano automatico" - Calendar Date; "Triskell Completo [Projecções Data início" - Project Beginning Date. "Triskell Completo Producao" -Project end Date
@campelliann , what is a difference in value without a second calculate? Here the second one is not adding any code. so not sure, if it is creating any difference
In this physical table, the values of the new column @totaldays would appear all in blank.
In the visuals, the totals would not appear without this second calculate. Weird.
User | Count |
---|---|
13 | |
12 | |
8 | |
8 | |
6 |
User | Count |
---|---|
28 | |
19 | |
13 | |
11 | |
7 |