I am having a very difficult time with a strange RB issue. Right now I sort of wish RB would go away real soon. :(
Very simple little report to total order $ by customer in one period (P1) and in a second period (P2) and print only if P1 total = zero and P2 total > 0. In essence to show customers that have not ordered in prior two years (or ever) but did order last month. Our definition of a new customer.
Periods are determined by parsing the report-filter for our dates: P1-Start, P1-End, P2-Start, P2-End
Because the parsing of the report filter requires running it through an aggregate I think this is confusing RB. When I try to total qualifying order line values and aggregate on customer I get the error "Reset level inconsistant for CustP1Sales". All the sorts and groups line up correctly. The agregates are pre-pass so I can test whether to print the customer footer. When I replace the parsed dates with bolted in dates it works fine so there is something about using the previous aggregated items in condition fields (test for if order is in period range) which are then used in a subsequent aggregation.
I can't pull up help for RB so if anyone has a definition for this error and/or some good ideas for getting around it I would really appreciate it. I have a hunch I've got this twisted enough to be beyond what RB can handle.
Thanks,
-Todd Caughey
Harvey Vogel Mfg. Co.
[Non-text portions of this message have been removed]
Very simple little report to total order $ by customer in one period (P1) and in a second period (P2) and print only if P1 total = zero and P2 total > 0. In essence to show customers that have not ordered in prior two years (or ever) but did order last month. Our definition of a new customer.
Periods are determined by parsing the report-filter for our dates: P1-Start, P1-End, P2-Start, P2-End
Because the parsing of the report filter requires running it through an aggregate I think this is confusing RB. When I try to total qualifying order line values and aggregate on customer I get the error "Reset level inconsistant for CustP1Sales". All the sorts and groups line up correctly. The agregates are pre-pass so I can test whether to print the customer footer. When I replace the parsed dates with bolted in dates it works fine so there is something about using the previous aggregated items in condition fields (test for if order is in period range) which are then used in a subsequent aggregation.
I can't pull up help for RB so if anyone has a definition for this error and/or some good ideas for getting around it I would really appreciate it. I have a hunch I've got this twisted enough to be beyond what RB can handle.
Thanks,
-Todd Caughey
Harvey Vogel Mfg. Co.
[Non-text portions of this message have been removed]