Ir al contenido principal

How to create an additional line text (ACLOB) on purchase orders for internal notes


Kyle Klinger
Sin conexiónhace 1 día
I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to. 
If you have a better way, please share.   
  1.  Add column to PORDERQ; YLINTEX2, Type TXC 
    1.  Save and validate table
    2. This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX
  2.  On screen POH2
    1. Add column YLINTEX2, to Block 1.
    2. Most likely you will want this field to be hidden.
    3. On column NBLIG add a button action ACLOB2, description "Text internal"
    4. This button action will require an action parameter "CODE2", it will not be available until after save.
    5. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added. 
    6. Save and validate the screen
  3. Custom code in SPEPOH
$ACTION
  Case ACTION
    When "ABANDON" : Gosub ABANDON # YK001 kklinger@lucidconsulting.com
    When "INICRE_LIG" : Gosub INICRE_LIG # YK001 kklinger@lucidconsulting.com 
    When "INIMOD_LIG" : Gosub INIMOD_LIG # YK001 kklinger@lucidconsulting.com 
    When Default
  Endcase
Return
$INICRE_LIG
  Gosub CHARG_TEXT_LIGNE
Return
$INIMOD_LIG
  Gosub CHARG_TEXT_LIGNE
Return
$ABANDON
For I=0 To [M:POH2]NBLIG-1
  If left$([M:POH2]YLINTEX2(I),3)="POQ" & [M:POH2]CREFLG(I)=0
  Call SUP_CLOB([M:POH2]YLINTEX2(I),WRETOUR) From TRTX3TEX
Endif
Next I
Return
$CHARG_TEXT_LIGNE
If [M:POH2]YLINTEX2(nolign-1)<>""
  If left$([M:POH2]YLINTEX2(nolign-1),3)="POQ"
    Call CRE_CLOB([M:POH2]YLINTEX2(nolign-1),GOK) From TRTX3TEX
    If GOK<1 Return : Endif
  Elsif !find(left$([M:POH2]YLINTEX2(nolign-1),3),"ITM","ITP")
    Call DUP_CLOB("POQ",[M:POH2]YLINTEX2(nolign-1),GOK) From TRTX3TEX
    If GOK<1 Return : Endif
  Endif
  [F:POQ]YLINTEX2=[M:POH2]YLINTEX2(nolign-1)
Endif
Return

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  Delete ,  R
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  server  specified in the command. When sending is launched by a work
Leer más