Identifying custom programs and forms in V 9.01

We are preparing for our V10 upgrade and wanted to know if anyone has a way to quickly identify all custom forms and programs on the Infor S3 V 9.01 platform. We never had that many but since it's been a long time since some were developed we want to make sure nothing is missed. Thanks.

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

If you have a method of developing custom programs with a custom system code such as "X" or "Y" or your company initials, you can search your productline directory for your custom code in the /**src folders. This only applies to 4GL/CASE code.

Example: If you developed a custom version of say, PA52, such as XA52, then the custom code would be in /pasrc (XA52PD, XA52WS, etc).

Now if you had custom Design Studio forms those would be in the /forms and /pages subfolders within /persistdata.

[Updated on 2/23/2016 5:04 AM]

unknown

[This is relevant for Windows/UNIX:] Also - specifically for "standard" supplied programs - when running an MSP you'll get a complete listing of all screens affected, with differences noted ... it specifically flags customized code with a "C" for Custom, because that code will NOT be updated with the new stuff. You can run in non-update mode just to get the listing, if you just want to see what was customized.

serafino

You should have a list someplace with the programs you modify, as well as the reason for modifying the code and a description of what you actually modified (along with comments within the code itself) whenever you do anything. Makes no difference if it's changing the text label on an S3 form field, cloning and rewriting an entire PD, or inserting functionality. You should have this documented for easy reference and to avoid losing this battle with every upgrade or patch. You might want to start this practice with your V10 installation because if you in any way customized V9, I can guarantee you're going to customize V10 -- and maybe not in the same ways.

unknown

Milo - We have not done an MSP in quite a while, do you remember if the references to custom programs are recorded in Lawappinstall.log or somewhere else? Thanks.

unknown

You can look at the preview.log

unknown

Yes, Brian is right. It's in Preview.log. When there's a customization, there's an "M" for "Modified" put after the version number in the Existing Version column. But it's hard to scroll through a huge listing. So for your convenience, at nearly the bottom there are sections labeled "Known modifications" and "Possible modifications" where they throw whatever they found up above. Check the "KEY TO SUMMARY" where the notation codes are explained.

martin-doherty

Changing Lawson vanilla code has always been a 'no-no' as a consultant! One should copy a program -giving it a name which identifies it as custom, and putting the mods in it. If a patch comes thru and updates the vanilla program, you can certainly compare the 2 codes to see what has been changed.
Keep a list!
I have non-lawson system codes to store all my customizations. It certainly makes upgrade time much easier.

unknown

When comparing changes between vanilla and custom coded versions of programs, (after patches etc are applied), don't forget to check the underlying program libraries too! Library changes have affected some of our custom code before... not often but it is something you need to be aware of.

unknown

Correct, and as some others have pointed out we would never modify the production delivered code.
Is there a method to regenerate preview.log on demand?
The last on I have is several years old.

moellerg

Really, the only way that I've found to generate a preview.log file is to preview a patch. I think that's where the suggestion of previewing a MSP is coming from.
That way you'll likely touch most if not all of the programs, and be able to see the modifications that you have potentially made.
lawappinstall preview .

Copyright © 2025 Infor. All rights reserved.