Hi, community.
I have a weird problem with my metrics sheet and the dashboard linked to it since it is displaying fault information with a specific formula. I have tried a lot of workarounds, including the update of both source and metrics sheet and a lot of different formulas but I can't still fix it.
Formula is as simple as: =COUNTIFS({Dropdown list 1}, "Element 1", {Day}, [Primary Column]@row). Dropdown list 1 is a single selection list with 6 or so elements; Primary Column contains a list of values from 1 to 31 (for each day of the month), and Day is a column containing the following formula: =VALUE(MID(Date@row, 1, 2)); where Date is a column with Date of creation (I have tried both an automatic column and a date column with an automation).
With this, I'm expecting to count the amount of Element 1 rows created per day for the month. Problem is, if I don't come into the source sheet and save it every time a new element is created, the formula gets corrupted and displays weird information. It will display things like counting 25 elements on day 2 when current date is february (2) the 25th (25) and everything else in 0.
To clarify: I am not using Today() formula absolutely anywhere, I'm already using automation to block and unblock new rows to update the source sheet and another automation flux to update the metrics sheet similarly (none of these interfere with the data nor the formulas). Also, I haven't reached the cell nor reference limit in either sheets.
I am hoping to find a real fix for this, since it is not an error with my formula but rather a bug in Smartsheet and manually updating source and metrics sheets is practically impossible in my specific situation because my solution involves around 16 sheets with this behavior and every single one of them is constantly receiving new data along the day (some even have 3 or more inputs in less than an hour) and every time, the metrics sheet gets bugged again.
I'm already sending a ticket to Smartsheet but since they usually take a lot to reply, I brought it here to see if anyone knows how to fix this.