Sage 100

If you DFDM the file there isn't an issue with lower vs upper case or if the UDF was imported, there isn't the dreaded unprintable character at the end of the field?

@Beth Bowers  The data is all upper case and looks perfect in DFDM.  I was able to re-create the issue on my office test system.

If you DFDM the file there isn't an issue with lower vs upper case or if the UDF was imported, there isn't the dreaded unprintable character at the end of the field?

Ruh Roh...

@Beth Bowers  The data is all upper case and looks perfect in DFDM.  I was able to re-create the issue on my office test system.

If you DFDM the file there isn't an issue with lower vs upper case or if the UDF was imported, there isn't the dreaded unprintable character at the end of the field?

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

Thanks @Kevin Moyes!  That's great information. 

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

Post back on what the SR Advisor advises

Thanks @Kevin Moyes!  That's great information. 

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

Thanks @Kevin Moyes!  That's great information. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 04-17-2024 15:36
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I had a hunch... the Options on the report screen were filtering based on the transaction data, not the vendor records. 

What I find truly odd is that an AP_Vendor UDF shows up in the selection grid, when selection grid fields should be based on the AP_OpenInvoice UDF (since that is the table the filter applies to).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 04-17-2024 16:34
From: Doug Higgs
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

Thanks @Kevin Moyes!  That's great information. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 04-17-2024 15:36
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Yes.  My initial thought was that the UDF on the selection screen was from either the OpenInvoice or maybe the TransactionPaymentHisory table.  I looked and the AP_vendor UDF was never mapped so that blew that theory.  Although it doesn't makes sense to add a UDF to the selection at least there is a viable work around.  Easy enough to create and map new fields and maybe we can wait a few weeks o populate the records after most of them have been paid.

I had a hunch... the Options on the report screen were filtering based on the transaction data, not the vendor records. 

What I find truly odd is that an AP_Vendor UDF shows up in the selection grid, when selection grid fields should be based on the AP_OpenInvoice UDF (since that is the table the filter applies to).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-17-2024 16:34
From: Doug Higgs
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

Thanks @Kevin Moyes!  That's great information. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 04-17-2024 15:36
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I think I encountered this some time ago.  I added a UDF to the customer master.  It appeared in the selection grid for open invoices.  Didn't work.  Didn't research it to the extent that @Doug Higgs did.  Big shout out to Doug for following it down the rabbit hole!

Doug, did Scott mention when a patch would be forthcoming?  Plenty of time until PU1 release, but my guess is the PU patches are in place.  I hope I am wrong.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
------------------------------


Original Message:
Sent: 04-17-2024 19:01
From: Doug Higgs
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

Yes.  My initial thought was that the UDF on the selection screen was from either the OpenInvoice or maybe the TransactionPaymentHisory table.  I looked and the AP_vendor UDF was never mapped so that blew that theory.  Although it doesn't makes sense to add a UDF to the selection at least there is a viable work around.  Easy enough to create and map new fields and maybe we can wait a few weeks o populate the records after most of them have been paid.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 04-17-2024 16:55
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

I had a hunch... the Options on the report screen were filtering based on the transaction data, not the vendor records. 

What I find truly odd is that an AP_Vendor UDF shows up in the selection grid, when selection grid fields should be based on the AP_OpenInvoice UDF (since that is the table the filter applies to).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-17-2024 16:34
From: Doug Higgs
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

Thanks @Kevin Moyes!  That's great information. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 04-17-2024 15:36
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

I think I encountered this some time ago.  I added a UDF to the customer master.  It appeared in the selection grid for open invoices.  Didn't work.  Didn't research it to the extent that @Doug Higgs did.  Big shout out to Doug for following it down the rabbit hole!

Doug, did Scott mention when a patch would be forthcoming?  Plenty of time until PU1 release, but my guess is the PU patches are in place.  I hope I am wrong.

Yes.  My initial thought was that the UDF on the selection screen was from either the OpenInvoice or maybe the TransactionPaymentHisory table.  I looked and the AP_vendor UDF was never mapped so that blew that theory.  Although it doesn't makes sense to add a UDF to the selection at least there is a viable work around.  Easy enough to create and map new fields and maybe we can wait a few weeks o populate the records after most of them have been paid.

I had a hunch... the Options on the report screen were filtering based on the transaction data, not the vendor records. 

What I find truly odd is that an AP_Vendor UDF shows up in the selection grid, when selection grid fields should be based on the AP_OpenInvoice UDF (since that is the table the filter applies to).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 04-17-2024 16:34
From: Doug Higgs
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

Thanks @Kevin Moyes!  That's great information. 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles


Original Message:
Sent: 04-17-2024 15:36
From: Kevin Moyes
Subject: Selection Field Doesn't Work in AP Cash Requirements Report

A quick test shows it's a bug.  UDF in AP_Vendor, but if you add that same UDF to AP_OpenInvoice, and add a value in the open invoice table, the filter works.

So, if your values don't change, you could flow the UDF value into AP_OpenInvoice (from all the various sources), update all historic AP_OI rows, and be done with it... or wait for a Sage bug fix.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON