Ir al contenido principal

Compile adonix source from a program

FUENTE ORIGINAL DEL ARTÍCULO 

BY  · PUBLISHED  · UPDATED 

We all know the main way to compile an adonix source:
in Sage X3 version 6.x and earlier, in fact, there is a special editor (ADOTRT function) available,
from where you can compile with the F7 function key or with the appropriate menu.

From 7.x, in the web interface there is still the ADOTRT function available, with the “Compile” button available,
but the F7 key is no longer available, and ESC-F7 escape sequence can not be used.

From version 7.x we also have Eclipse available through the pluging Safe X3.

But if for some reason we needed to compile a source from a program?
Or if we wanted to recompile all the sources starting with Y?

(By the way, you know that the changes made by the end customer should they start with the Z?
The Y would be reserved for consultant developments…)

To do this, the following call is helpful:

Call VALID(FOLDER,SOURCE, DOSSIER, OK) From VALMSKSUB

Where:

  • FOLDER is the folder where the file to be compiled is contained
  • SOURCE is the name of the file, which must have extension src, to be compiled (but the name must be indicated without extension, for example “SPESOH”)
  • DOSSIER is the name and dossier in which the folder is located: put nomap and it’s ok, except for special uses
  • OK is a variable of integer type to indicated if the compilation was successful

To compile all customized sources, we can do:

Local Char DIR(GDIMFIC), FILELIST(GDIMFIC)(1..100)
Local Integer LENG
DIR="C:\SAGE\"+nomap+"\TRT\Y*.src"
Call SYSTEME2 (adxmac(0),"dir /b "-DIR,"",LENG,FILELIST) From ORDSYS
Local Integer OK
For I=1 To LENG
  Call VALID("TRT",seg$(FILELIST(I),1, instr(1,FILELIST(I),".src")-1), nomap, OK) From VALMSKSUB
  Next
End

Some comments:

  1. nomap o nomap(0), it’s the same, returns the name of the current dossier
  2. seg$(STR, start, end) returns a substring of STR that starts from the character in start position, up to index character end
  3. instr(start, STR, find) search the string find in STR from index start and returns the position

Summing up

seg$(FILELIST(I),1, instr(1,FILELIST(I),".src")-1)

need to remove “.src” from the file name.

You could use other dos commands to already have just the name directly, but it was less fun!

 

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 ,  ...
Leer más

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

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes 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.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table 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  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
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  ...
Leer más