Skip to main content
Answer

how to use ‘belong to’ filter in acumatica report design

  • July 6, 2023
  • 3 replies
  • 221 views

Forum|alt.badge.img

how to use ‘belong to’ filter in acumatica report design

Best answer by sweta68

Hi @vannakheng,

The term "Belongs to" is not a standard filter type in Acumatica.

To achieve similar functionality in Acumatica report designer, you can use the "In" filter type. 

By using the "In" filter, you can achieve a similar filtering behavior as the "Belongs to" filter, where you can specify a list of values that the field should match.

 

Regards,

Sweta

3 replies

Forum|alt.badge.img+9
  • Semi-Pro III
  • Answer
  • July 6, 2023

Hi @vannakheng,

The term "Belongs to" is not a standard filter type in Acumatica.

To achieve similar functionality in Acumatica report designer, you can use the "In" filter type. 

By using the "In" filter, you can achieve a similar filtering behavior as the "Belongs to" filter, where you can specify a list of values that the field should match.

 

Regards,

Sweta


  • Freshman I
  • July 24, 2023

You state that BelongsTo is not a standard filter type in Acumatica but it is used in some reports.  For example in Payrol report PR641060.rpx it is used.  However, I cannot find any help on how it works.

( @OrgBAccountID IsNull       Or
  PRPayment.BranchID BelongsTo

@OrgBAccountID

  ) And

Fernando Amadoz
Jr Varsity I
Forum|alt.badge.img+2

I recently had this same question while working on the report designer with the ‘belongs to’ condition.

This is a very specific condition from the framework that is used to identify the Branches associated to a given Organization/Company’s BaccountID value.

All references to this condition in the standard Acumatica reports show the pattern Branch belongs to OrgBAccountID. Here is an example from one of the 1099 reports

 

What is occurring underneath during this SQL representation is that the parameter displays the one - or many - BranchID associated to said Business Account.

Notice that the SQL representation of the query converted the second parameter to this result:

AND [CompanyBranchBAccount1099_BAccountR].[BAccountID] = 7128 AND [AP1099History].[BranchID] IN ( 125, 29, 66))

Be aware that belongs to and IN are not the same. IN condition does not replace the value.
If we change the example above to use IN instead, this is the SQL representation (which will not print correct results)

AND [CompanyBranchBAccount1099_BAccountR].[BAccountID] = 7128 AND [AP1099History].[BranchID] IN ( 7128))