Skip to main content

We opted to use branches because we are technically a two branch company internally, however, as far as our customers are concerned we are one company, one branch. 

Because we opted for branches, the default customer statement (consolidated included) form wants to group AR documents by branch but this confuses our customers who expect all their documents in order by document date. This in spite of the AR Preferences consolidation setting set as below:

 

 

I attempted to remove the Branch group in the report designer, and while this fixed the sort order, the “...AgeBalance00-05” fields started calculating as though only for the first branch.

Further testing suggests the report was using the groupOrganization footer which does use the OrganizationAgeBalance00-05 fields rather than the customer equivalents, but both customer and organization are higher level groups than branch, so I don’t know why they would be recalculating as though per branch. 

Does anyone know how to keep branch configuration while removing branch grouping and maintaining the integrity of the footer totals?

Also have this question


@xkylewrightx I don’t know if you found a solution to this or not, but what I ended up doing was creating a sub-report based just on the ARStatement table that mirrored the footer of the original statement, and passing the customer and date to it to get the totals for both branches since I couldn’t ignore the branches and also get the variables to add up the totals properly. 


Thank you for sharing your solution with the community @martinxfe!


@xkylewrightx I don’t know if you found a solution to this or not, but what I ended up doing was creating a sub-report based just on the ARStatement table that mirrored the footer of the original statement, and passing the customer and date to it to get the totals for both branches since I couldn’t ignore the branches and also get the variables to add up the totals properly. 

We did the same and it works on a per-report basis when accessing through the Report form - however, we’ve noticed that the report breaks when using the Print Statements or Email Statements screen.

I was wondering if you managed to resolve this issue?


@xkylewrightx I don’t know if you found a solution to this or not, but what I ended up doing was creating a sub-report based just on the ARStatement table that mirrored the footer of the original statement, and passing the customer and date to it to get the totals for both branches since I couldn’t ignore the branches and also get the variables to add up the totals properly. 

We did the same and it works on a per-report basis when accessing through the Report form - however, we’ve noticed that the report breaks when using the Print Statements or Email Statements screen.

I was wondering if you managed to resolve this issue?

@kokjietan  We send statements in bulk via the Email Statements function and I believe ours is working. I don’t recall having to troubleshoot that issue, though. Can you describe a little more how it’s breaking?


Hi @martinxfe , Glad i came across your post.  I am currently working on the same scenario and i change my reports according to  the steps that you’ve provided above. However i am not getting desired results when i merge the sub-report with main report. Below is the brief explanation about my setup.                                                                                                                                                                                                                               On my main report i removed the branch filter to fix my date issue.                                                                                                                                      .

On my Sub-Report I have the branch filter.  All my sections are set to false except the footer sections.                                                                                                                   .

This is the results i get when i run the sub-report.      Which is correct.                                                                                                                                                             .

Below shows how i merged my sub report with the main report. I added the same report for all the footer sections.                                                          .

See the results below when i run the main report.                                                                                                                                                                   

   Would it be possible for you to kindly share a copy of the report attachment with me??                                                                                                                      


Hi @tkapuenene36 

I would get rid of the Branches group all together. If nothing else it declutters the design form. 

 

I have my sub-report in a secondary groupOrganization footer above the page number section. (Note: You would have to adjust which footer you used I believe based on how your company consolidates branches, orgs, and companies.)

 

The  sub report pulls three parameters: ARStatement.StatementDate, ARStatement.StatementCustomerID, and the branch parameter from the primary report( =o@Branch] ). (Including the branch parameter allows the report to still be branch filterable)

 

The sub report is just the ARStatement table filtered for the three parameters that were passed as below, and the OrganizationAgeBalances sum up the AgeBalances for each branch, spitting out the total. 

 

This much should establish a correct summary. 


Let me know if that helps. 


Reply