Detecting logically and/or syntactically errors within long and complex expressions is always quite hard. Therefore you should try to avoid it from the beginning and starting very simple, like:
count(Field) and then count({< SingleSetStatement >} Field)
and so on. If they work you could add the next step on complexity to it. It may look a bit cumbersome but it's quite common and a best practice approach - at least for all new/changed views - because beside getting a result you need always to verify that the results are correct and the simplest method is to calculate the intermediate steps in parallel and after they are working to merge them and checking it again.
Beside this your expression missed multiple brackets and it looked as if there were typos, too because I see FiscalYear and fiscalYear. Further just remove the date() which aren't needed to shorten the expression.
IMO you should also change the set analysis conditions itself - not querying dates else years or periods or a continuing period-counter because it would simplify the approach. There is even more possible by creating appropriate flags for the current/previous years/periods within the master-calendar. Here is a lot of background to it:
Beside the already mentioned missing brackets to close the set analysis (parts) - the last brackets before Distinct is also not set - you should simplify the statement, for example by removing the multiple date() functions because you compares with >= and <= against numerical values and there the formatting is irrelevant.
Detecting logically and/or syntactically errors within long and complex expressions is always quite hard. Therefore you should try to avoid it from the beginning and starting very simple, like:
count(Field) and then count({< SingleSetStatement >} Field)
and so on. If they work you could add the next step on complexity to it. It may look a bit cumbersome but it's quite common and a best practice approach - at least for all new/changed views - because beside getting a result you need always to verify that the results are correct and the simplest method is to calculate the intermediate steps in parallel and after they are working to merge them and checking it again.
Beside this your expression missed multiple brackets and it looked as if there were typos, too because I see FiscalYear and fiscalYear. Further just remove the date() which aren't needed to shorten the expression.
IMO you should also change the set analysis conditions itself - not querying dates else years or periods or a continuing period-counter because it would simplify the approach. There is even more possible by creating appropriate flags for the current/previous years/periods within the master-calendar. Here is a lot of background to it:
