Ir al contenido principal

Personalizing General Parameters in Sage Enterprise Management (Sage X3)

Personalizing General Parameters in Sage Enterprise Management (Sage X3)
Did you know there’s a function in Sage Enterprise Management (Sage X3) that gives you access to all user-centric parameter values?

As a reminder, parameter values are parameters that can be managed at multiple levels (folder, legislation, company, user) that are driving the behavior of the application. For example, depending on parameter values, users will see a default entry transaction screen in the journal entry function.

Some other behavioral changes will be related to how the system uses default journal codes when running through end-of-month processes.


Here's how to go about personalizing general parameters in Sage Enterprise Management.


personalizing general parameters in Sage Enterprise Management (Sage X3)
 personalizing general parameters in Sage Enterprise Management (Sage X3)

Instead of having all user levels’ parameters maintained by the system administrators at the folder level, there’s a function that allows users to change and modify some of those values based on their preferences.
One of the great things about these parameter values is that the selected ones are very safe. Doing this does require some training, but once it’s made clear how to navigate those screens, you’ll be glad you did.

Since this is its own dedicated function, you’ll be able to give or deny access based on security rights.
You can find it under Usage > Users > Personalization.


personalizing general parameters in Sage Enterprise Management (Sage X3)

Request a Sage Enterprise Management (Sage X3) Demo »


Once in, you can scroll through the different pages and find the ones you need.

personalizing general parameters in Sage Enterprise Management (Sage X3)


For the above user, you can see that no entry transaction is defined as the default entry transaction when getting into the journal entry screen; if the user repeatedly uses the same entry transaction, selecting one as a default will save a step in the process.


If you need something to be defaulted, chances are you’ll find it in the parameter values; this is one of the many functions that make Sage Enterprise Management so flexible and convenient to configure – this feature, among others, really empowers users to make the solution theirs.

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