Sage 100

I want to require an entry to a UDF field. The field is located in the AR Invoice Detail table and on the AR_Invoice_PLines panel. I think I can set a ""required"" attribute in the UDF definition. However, I am concerned what might happen with all the records that currently exist in the file that don't already have a value defined? The client has been using Sage 100 for years and we just added the UDF earlier this year. Therefore there are hundreds of thousands of records without a value. Is there another way to make a UDF required in a detail entry grid format?

Shawn, you would set it as required in AR_InvoiceDetail table (data entry) and I assume you wan that to flow to the history table but don't set it as ""required"" in the AR_InvoiceHistoryDetail table.

Are you wondering about AR invoice history detail??

@DavidOverholt thank you for the kick in the pants. It won't be a problem in I make it required in AR Invoice entry and not be required in history. Now make it more fun. What if we do this in SO entry? Since history is not separated from current, is there a way to make this required in SO?

You can in Advanced Fields settings, but only for text type fields.

It seems the answer would still apply wouldn't it? in SO_SalesOrderDetail you make it required but then in the SO_SalesOrderHistoryDetail you don't make it required? Maybe I'm missing something though.

I think in SO there are many more open orders and the issue is when you go into the detail you'll be forced to enter a UDF

yes, if they have a lot of open orders then that would be a big issue. Maybe import them into the UDF? important side note when making fields required in SO Header. Be sure to set the data source for those UDFs to populate when your updating the sales journal (SO_SalesJournal_upd) if you don't and the order has backordered lines then the backorder does not get created because the required UDF is not populated. You get no error messages or anything helpful like that either! I made that mistake on the header in the past. I would assume similar issue would happen on the detail UDF if it is required, but I have not tested it.

You also need to be careful when you make a field ""required"" - I one time made that mistake and it locked things up