I'm trying to understand how the Errors by Target on the Transform > My Reports > All Reports (by Object) page works. I have created an Error source report and published it. It shows up when I click on All Reports, but not when I click on Errors by Target. Can someone please clarify the purpose of this function and how to set it up?
-
Best answer
VGazquez: Hi Greg, On Errors by Target there is only one report: Target Error Aggregate Report. Is a summary of errors on a target and is not registered. It is a report that is automatically generated and it aggregates the key information from every error report (Error, Target Readiness and Business Readiness report types) that is registered to the target. There is one Target Error Aggregate Report per target. This process also includes Target Data Services and Target Reports of type errors. As far as I know, this report only contains Target Report, not Target Source Reports. So in your case, if the report you created is a source report, then it will not be there. I was about to open it as an Idea (I faced the same need) but you already posted. I recommend to anyone who think it is a good idea to VOTE it: https://dsp.ideas.aha.io/ideas/MIGRATE-I-178 Regards
0 -
Thanks Victor. Apparently there is another step that is required before the report will populate. I think you have to Refresh Error Aggregate Cache on the Vertical View of the Target. Once I did that, included the keys from the target in the report and re-processed it, the aggregate report then displayed. It appears that only Error reports are included (not Target Readiness, etc.), which is what I wanted, but not how you described? I like the enhancement you suggest to the proposed report in the Ideas Postal. Greg
0 -
Final Answer: 1) ONLY Target Reports will be included in the aggregate error report, not source reports 2) Reports with zero record counts will NOT be included 3) Error, Target Readiness and Business Readiness report types are included 4) If a report changes, it must be re-processed and new aggregate error report generated 0
Please sign in to leave a comment.
Comments
3 comments