25R1 Still problems with Binding

Hello,

These fields can join to AR Adjust table:

ARAdjust.adjgDocType  is Adjusting Doc Types:  Credit Memo or Payment.   

ARAdjust.adjgDocType is Adjusting Reference Number:  Credit Memo Reference Number or Payment Reference Number.  

adjdRefNbr and adjdDocType  “Adjusted” refers to the PAID documents - Invoices.

HTH

Thank you — I confirmed adjgRefNbr and adjgDocType are the correct fields on ARAdjust to join to ARPayment. However in my 25R1 Generic Inquiry these fields return 'multi-part identifier could not be bound' error even though they appear in the field dropdown. Has anyone encountered this in 25R1? Is there a workaround for joining ARAdjust to ARPayment in a GI?

Hello,

Please show your joins on the Relationship tab of your GI so we can help you. Thanks.

Hi ​@swhitley,
Add relation as below screenshot and let us know if it works for you.

In addition to the example shown by Dipak, the Join Type could be Inner or Right, depending on whether you want un-applied Payments to be included in your GI.

Please describe what you want to include in your GI or give an example. Thank you.

Thanks!  I don’t want unapplied payments included.  If it’s unapplied, it’s in process or there’s an issue that needs to be resolved.

Thank you all — very helpful. Based on your many-to-one guidance, should our complete join chain be structured as: ARPayment → ARAdjust → ARInvoice → PMProject? We are using PMProject as our primary/anchor table currently. Should we change the primary table to ARPayment instead, or can we keep PMProject as primary and reverse the join directions? 

In Acumatica 25R1 Build 25.101.0153.9, every field on ARPayment table returns 'could not be bound' when used as a parent table in a GI relation. Fields including docType, refNbr, DocDate, CuryID all fail. ARPayment works fine as a child table. Is ARPayment restricted as a parent table in 25R1? Is there a workaround or substitute table to use for getting actual cash received by project?