You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to run the exportToJson.R code, an error message kept occurring. In looking into the code within this file, we noticed that the allReport functions appear to be ordered alphabetically. We think that our error was generated as a result of this ordering, specifically, the generateDashboardReport function occurs before the generatePersonReport, but it seems that the DashboardReport is dependent upon thePersonReport functioning having already been ran. When we moved the generateDashboardReport function to the end of the file we were able to successfully run the code (although we are unsure if the output is correct). Could there be another reason as to why we are experiencing this error?
The text was updated successfully, but these errors were encountered:
Good catch! We identified this issue ourselves: I introduced this error when adding functionality to run individual report exports, and I had to keep track of the report identifiers I put in. So, I sorted it alphabetically to keep track of that, but forgot that the dashboard report must appear last.
So, I've checked in this fix, and you should be able to pull latest code and regen.
When trying to run the exportToJson.R code, an error message kept occurring. In looking into the code within this file, we noticed that the allReport functions appear to be ordered alphabetically. We think that our error was generated as a result of this ordering, specifically, the generateDashboardReport function occurs before the generatePersonReport, but it seems that the DashboardReport is dependent upon thePersonReport functioning having already been ran. When we moved the generateDashboardReport function to the end of the file we were able to successfully run the code (although we are unsure if the output is correct). Could there be another reason as to why we are experiencing this error?
The text was updated successfully, but these errors were encountered: