Payment Method GUID

Hi ​@Jupiter ,

The GUID you're looking for is the NoteID field on the CustomerPaymentMethod DAC (table CustomerPaymentMethod).
Here's what you need for your Generic Inquiry:
- Table (DAC): PX.Objects.AR.CustomerPaymentMethod
- Column: NoteID
This is the system-generated GUID that the API returns when you create a customer payment method record. Every record in Acumatica that supports the INotable interface has a NoteID which serves as the record's unique identifier (GUID) used by the Contract-Based API.
To set up the GI:
1. Go to System > Generic Inquiries (SM208000)
2. Add CustomerPaymentMethod as a table in the Tables tab
3. In the Results Grid tab, add the NoteID field from CustomerPaymentMethod
4. You can also add other useful fields like BAccountID, PaymentMethodID, Descr, PMInstanceID, etc.
The NoteID is the same GUID value that the API returns in the id field of the response when you create or query a Customer Payment Method via the REST API (e.g., PUT /entity/Default/24.200.001/CustomerPaymentMethod).

Hope above helps!!

Awesome ​@Rakshanda , thank you very much for the above details.  I did manage to add the column, but given my limited knowledge on GI’s, couple more questions. 

• How can I change the column header in the Results Grid, currently it is showing as ‘CustomerPaymentMethod_noteID’ and I want to change to some text?
• Also, while changing one of our GI, I got this obsolete error which is confusing, because the GI still works and customer customer data and I can see all columns from that Table in Results grid.  So not sure why the warning and this is in 2023R1.

Hi ​@Jupiter ,

1. Change the Column Header

• Go to the Results Grid tab.
• Select the required field, such as CustomerPaymentMethod.NoteID.
• Change its Caption to the text you want to display.
• This changes only the column header; it does not change the actual DAC field name.

2. Obsolete BAccountR Warning

• BAccountR is an obsolete DAC.
• Existing GIs using it may continue to work, which is why the data is still displayed correctly.
• For new GIs, use BAccount instead of BAccountR.
• After replacing it, verify the Relations and Results Grid to ensure the same data is returned.

Thank you ​@jinin , much appreciated.