Sage 100

100 v2016 Advanced - Created a ""LOCATION"" UDF in AR_Customer. Mapped it to ""LOCATION"" in AR_CustomerMemoWrk. Added the LOCATION field to the Customer Memo Printing report. The LOCATION prints on the report. When I choose the operand ""Equal to"" and enter GREENVILLE or any of the other location I get a ""Data not Selected for Printing"". I have also tried ""Contains"", ""Range"" and other operands with no success. I tried rebuilding the AR sort files. Any ideas would be appreciated.

Is it stored upper-case? What does the data in UDF_LOCATION look like when you DFD&M AR_Customer?

Yes. The UDF is being stored as upper-case. I checked a couple of AR_Customer records in DFDM and verified it is upper-case.

I have tried using a range of locations, such as aaaaa to zzzzzz and this also gives a ""No data is selected.... "".

The plot thickens...It doesn't work for me either in Sage 100 2016, PU 4. As soon as I try to filter using a AR_Customer UDF, 'Data not selected...'.

Oh boy. Who do I bill for the time I just wasted on a custom report that doesn't work?

I know, I know, @WayneSchulz and @JerryNorman I should have a knowledge transfer agreement in place and I wouldn't have to worry about it.

OK, it looks like Customer Memo Printing is looking at UDFs that are supposed to be in AR_CustomerMemo. Once I copied the value into my UDF there, it worked as expected.

Quick VI Export from AR_Customer and VI Import into AR_CustomerMemo and you should be good (hopefully).

@DougHiggs - Wasted effort is wasted effort. Doesn't matter if you have a KTA in place. What I would be pissed about is that this wasted effort takes away from valuable karaoke rehearsal time that you may need for the upcoming Summit.

@SteveIwanowski This is messed up. If you add an AR_Customer UDF and that UDF gets added to the Customer Memo Printing pick screen, you would expect this pick screen selection to be associated with the AR_Customer UDF. The customer doesn't want to have to modify the LOCATION field in both Customer maintenance and Customer Memo Maintenance whenever there is a new customer or a location change.

What if you link the AR Customer UDF to the customer memo printing report? Also add a parameter to the report to prompt for location?

@JeffSchwenk I will be busy ordering booze for you so we can get an encore performance of this years concert.

@JeffSchwenk ""What if you link the AR Customer UDF to the customer memo printing report?"" That's what I did. That;s how it is now and it doesn't work. Apparently you have to also create a UDF in Customer memo and populate all of the data there. This may make it work but if the user doesn't keep the two table in sync then we will get a report with invalid data. I don;t like it at all. This seems to be a bug... not working like it should.

Yeah, it's definitely wonky. I'm with Jeff; if that's the only field they're filtering on, just join AR_Customer in and filter as a parameter inside Crystal (while you wait on hold with Sage)...

If it was a stand alone report without a ProvideX front end, this would be OK. However, I cant just set up a parameter to prompt the user from this report. It would have to be a hard-coded select by LOCATION. The user wants to print memos by individual location. I need to think about this. The best solution may be to just sort the report by the new location code and not use the selection. Thanks for you help guys.

Yes, being a karaoke rock star certainly has its advantages..... Me and Mick and Rod!! What can I say?

@JeffSchwenk I see what you mean now. Link AR_Customer to AR_CustomerMemoWrk. That is a good idea, and I have tried that. Unfortunately it still doesn't work. the bug is that the pick screen is looking to AR_CustomerMemo for the select data and not finding it. The ProvideX pick screen is looking SHOULD be reading the UDF in AR_Customer not AR_CustomerMemo. This is messed up.

You would not enter anything to filter on the ProvideX screen, just in the Crystal parameter. Then it should work.

Hard code GREENVILLE as the parameter and train the user to modify Crystal to change the location as necessary?

No, tie the Crystal parameter to the AR_Customer.UDF_Location, and the use that parameter in the Crystal Select statement. So the Wrk table will have every memo, but Crystal will only show the Location matches.

I will try it.

AFAIK, the select grid is always tied to the report's main table, which in this case is customer memo. WAD.

@KevinMoyes If that is WAD then it is a horrible design. If I add a UDF to the AR_Customer table the UDF appears as a selection value on the Customer Memo printing report. Customer Memo printing uses AR_CustomerMemoWrk.

If that is WAD then it is a horrible design."" Agreed 100%, but that is what I have found with the selection grid for all reports, not just this one.

Yeah, the issue is that you can't source the AR_CustomerMemo UDFs from AR_Customer. Which is ironic since AR_CustomerMemoWrk can...

@DougHiggs - Time for a shot of tequila!!!! It helps to get the foul tasting WAD off your palette.

LOL... For sure. Make it a double!