Ir al contenido principal

How to Perform Mass Updates in Sage Enterprise Management (Sage X3)

Have you found yourself in a situation where you need to change many records in your database at the same time? Perhaps you hired a new salesperson and you need to assign several customers to them, or a new territory opens up and you need to re-align more than one customer to that territory.

These are scenarios where a “mass update” utility can really help. Think of a mass update as a graphical interface to run a SQL query that will update the database based on WHERE clauses. So, for example, you can retrieve all customers WHERE the STATE = FL, GA, AL, MS, and NC and change the TERRITORY field for all these customers to “Southeast U.S.”

The above is just an example; the possibilities are endless. The beauty of a mass update utility is that a user doesn’t have to be “technical” or know SQL. The idea is that you’re simply using the formula wizard to build your conditions.


This utility is a real time saver because the alternative would be to either make the change manually, record by record, or to require a technical person to go into SQL management studio to perform this task. These people are usually very busy or very expensive – usually both.

With this utility, you can run the query directly from within Sage Enterprise Management (Sage X3) using their formula wizard, which is available in all versions of Sage Enterprise Management.

Here’s how to perform mass updates in Sage Enterprise Management.

Mass Update Definition

Development > Processing dictionary > Update transactions

The goal is to replace a sales rep with another one for all customers.

mass update in Sage Enterprise Management (Sage X3)

Mass Update Usage

To execute the mass update, go to Development > Utilities > Miscellaneous > Database Mass Update, or call function AMIEXE directly.

Batch Server

Usage > Batch server > Recurring task management

This task could be scheduled on the batch server using code AMIEXE, in which case you’d have to specify parameters.

mass update in Sage Enterprise Management (Sage X3)

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