We are in the process of implementing OpTime for our OR patient billing and we need to interface information that is currently not stored in Lawson. The plan is to enter 6 different pieces of information in user fields on IC11 and IC12. Is it difficult to maintain the customized format of these fields with patches and upgrades? Is there anyway to change the label on these fields so that they display on the form with the correct label? Is there any way to change these field names in the database so when reporting thru Excel Addins and Crystal the user is able to easily identify the data being queried?

Is anyone else using customized user fields?

Hi SheilaZ,

Yes and No.
There are a couple of ways you can change the field labels on the screen. I would say the safest and most Lawson recommended way is to use the design studio tool and change the labels to your heart's content. You can also set default values and do some edit checks and a couple of other things with that tool.

No as for changing the names in the database. Well its possible, but it is such a bad idea that I will just say that its impossible. You're much better off learning which field User01 is referring to than having to deal with the consequences of renaming the DB field.

Hope that answers your question

I have seen design studio and have worked with it in training but we are not on portal yet. Is there anything we can do in LID?

Yes but with LID you'll need to recompile the program.

Here's what you do. Pull up the .scr file for the screen you want to modify, It will be easy to find the section that has the labels. Change the labels, save the file, recompile, and you're ready to do.

Obviously back up the file before you start.

Let me know if you want details on each step. If you want to attach the .scr file and the mods you want made for it, I'll do it for, it will take a minute.

Remember that any custom changes you may have to be modified each and everytime a patch is applied that impacts that screen.

Modifying the .scr is the solution that we used as well, when we needed to relabel user fields. It's very quick and easy to do. It's also about the lowest-impact customization that you can do in Lawson.

If you have to go further and track more information than there are fields, the safest method is to add another database file. (We have had to do that also.) But the customization was somewhat more complex. It takes a real programmer to do that.

Keeping careful documentation on what was changed is key. A CTP or MSP can wipe out the changes.

-- Milo --

I agree, I find too many clients are too afraid of making minor code changes and they go the route of some add-on solution. Which is fine but keep in mind if you're keeping track of your changes and they're just simple changes like this its not likely you'll ever have a problem with it.
Also keep in mind that doing any kind of change requires you to review that change during an upgrade or patch ... So whether you do it this way or any other way the support stays the same. In fact as Milo said, this is about the smallest change you could ask for and you're very unlikely to come across any issues in the future.