• Search Forums
    Advanced Search
Prev
Next
Forums User Experience Lawson Design Studio

Best Practices

 2 Replies
 0 Subscribed to this topic
 13 Subscribed to this forum
Sort:
Author
Messages
Angela Collins
Basic Member
Posts: 20
Basic Member
2/2/2011 4:29 PM
Much of the Javascripting references the field ID.  OnBlur uses the field ID as well as several others.  How do you make it easy to maintain since the field numbers can change with patches?  Our thought was to put as much of our customizations in Javascripting because when customizing the COBOL, that normally gets the response that the customization is the issue.
Ragu Raghavan
Veteran Member
Posts: 477
Veteran Member
New Poster
New Poster
Congrats on posting!
Engaged Poster
Engaged Poster
Wow, you're on a roll!
Avid Poster
Avid Poster
Seriously, you're a posting maniac!
Engaged Reader
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader
Avid Reader art thou!
2/2/2011 5:14 PM
Sorry Angela. I must be misunderstanding something.
Let us say field "text1" is used for Company and is linked to the field PCT-COMPANY in PA52, that kink is going stay in place in the XML file even after an upgrade. The only event I can think of, when this would break is if Lawson changed PA52, so the company field is no longer PCT-COMPANY and is called ZZZ-COMPANY or something.
Angela Collins
Basic Member
Posts: 20
Basic Member
2/2/2011 7:04 PM
The problem is that the fields number can change.  Then, you have to hunt through the code to find out which field numbers changed.