Wheres my field (GL20)?

Sort:
You are not authorized to post a reply.
Author
Messages
mondrar
Advanced Member
Posts: 35
Advanced Member

    I made a change to the file GLADDRESS, and added a fourth user field that I would like to use on the GL20. I did the usual dbdef, blddbdict, and dbreorg. The new field is in GLADDESS, field name (OPTFIELD4), and now I would like to add it to the form GL20 using design studio. I usually start from scratch when creating new forms, but this time, I would just like to add this one field. When I go to the GL20, add a new text box, and look for the new field I added, it is not there. Is this the proper procedure to use, or am I suppose to be using the CASE tool PGMDEF to add this field to the form before design studio can see it. You would figure it would be available to select and add in design Sudio.

    Thanks for the help in advance...

    John Henley
    Senior Member
    Posts: 3348
    Senior Member
      You have two options:
       
      - You can add it to the GL20.scr (and add the underlying COBOL logic to get/set from GL20Fx-XXX to GLADDRESS).  Once that is done, you should see the field in LID, and then you should be able to easily add the form via Design Studio. 
       
      - You can code up a set of DME / AGS calls within the Design Studio form to get/set from/to GLADDRESS.   
       
      Regardless, what you are doing is what I categorize as a "modification", and therefore is subject to maintenance issues down the road -- i.e. it will be overwritten by future CTPs, MSPs, etc. 
       
      Why don't you just use an attribute instead???
      Thanks for using the LawsonGuru.com forums!
      John
      mondrar
      Advanced Member
      Posts: 35
      Advanced Member

        This might be a stupid question, but what is an attribute in Lawson?

        John Henley
        Senior Member
        Posts: 3348
        Senior Member

          It's a way of creating a user-defined data element attached to a record...Lawson provides that capability for a number of reference items (i.e. vendor, customer, accounting unit, account) as well as AC and GL transactions. 

          Now, I have to scold you, and don't mean to offend you, but if you don't know what an attribute is, you probably have no business making the afore-mentioned modification to such a core table in Lawson without understanding the future ramifications.

          Thanks for using the LawsonGuru.com forums!
          John
          mondrar
          Advanced Member
          Posts: 35
          Advanced Member

            I concur, no offense taken...

            You are not authorized to post a reply.