Aaron
08/13/2025, 1:31 PMCeligo AI
08/13/2025, 1:31 PMAI generated answer (using internal Slack threads):****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The issue you're experiencing with the reference row in the financial report could be due to a few reasons. 1. Large Data Set: The error message "invalid reference row. the results of income statement referenced report are too large" suggests that the data set being referenced is too large for the report to handle. This could be due to a large number of transactions or a complex calculation in the report. 2. Incorrect Reference: If the report columns have been changed or if the report is referencing the wrong net income from the Profit and Loss statement, it could lead to this error. 3. Column Removal: If the amount column was removed and then re-added, it could cause issues with the report. Once the amount column is removed, it can't be re-added in the same way and the report would need to be recreated from the base version. 4. Drill Down Settings: If the rows are set to disallow drill down, it could lead to this error. Make sure the rows are set to allow drill down. 5. Inactive Custom Segment: If the reference is an inactive custom segment but you want the custom segment to be blank and it's being forced to have a value, it could lead to an invalid reference key error. Please check these points and adjust your report accordingly. If the issue persists, it might be necessary to recreate the report from scratch.
Celigo AI
08/13/2025, 1:31 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.815605044
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.802074254
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.799756765
Celigo AI
08/13/2025, 1:31 PM