Ir al contenido principal

Add a Column to a Left List


I assume you have already read my Sage ERP X3 Day 1 blog and have some understanding of the definitions of certain terms I will refer to here and in future blogs. In this blog I will be outlining how to add a customer name column to the Left List on the Orders entry window. First let me show you where I am looking to add this column. This is in the Orders entry window.
I consider this an enhancement to the base install of Sage ERP X3 not a customization. This is just using the native functionality of Sage ERP X3 toolset or framework, also referred to as SAFE X3. This is not altering existing or creating new X3 code per se.
So you need navigate to go the Sage ERP X3 Objects in the Development module. This can be found in Development>Processes>Objects. As a refresher to definitions, a Sage ERP X3 Object is a collection/repository to group the environment that will be presented in a Window. The Window
Select Object SOH, on the Selection tab at the bottom of the grid right-click on Row 3 as shown below. Select Insert Line. Enter the Table SORDER and Field BPCNAM. Tab across the fields. Save your changes. Then you need to perform Validation on the screen to publish the change.
NOTE: If you want to look-up any values in the fields in the prior paragraph you can right-click to do a Select.

This shows the above grid after adding the Customer Order Name field for the Left List Selection.

Now go back to your Orders screen shown above. You will now see the newly added column in the Left List.
You can do this for any of your Left List.
I hope you found this helpful!

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 ,  ...

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

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  ...