Ir al contenido principal

How to use time and date

 

Fuente original del artículo: SAGEDEV

Let’s see today how to use time and date in Sage X3.

To get the current date in a Date variable, use the date$ function.
In the same way to have current date and time in a Datetime variable, use the datetime$ function (only from V7 release).
The established form to represent date and time with a string is:

YYYY-MM-DDThh:mm:ssZ           #attention to the letters T and Z

Typically date and time have “YYYY-MM-DDThh:mm:ss” format

num$(date$)                   #To get today's date string
num$(time$)                   #To get the current time as a string
num$(datetime$)               #To get today's date and time as a string
gdat$(DAY,MONTH,YEAR)         #To get a date of a day, month and year
gdatetime$(str)               #To get a Datetime variable from a string
year(date)                    #To get the year of a date
month(date)                   #To get the month number of a date
month$(date)                  #To get the month name of a date in the current language
day(date)                     #To get the day number of the month (1-31)
day$(date)                    #To get the name of the day of the week
dayn(date)                    #To get the day number of the week (1=lunedì, 7=domenica)
week(date)                    #To get the week number (1-53)
nday(date)                    #To get the number of days passed since January, 1600\
nday$(NUM)                    #To get a date from 1 Jan + a NUM of days
eomonth(date)                 #To get the last day of a month

You can also perform simple operations:

Local Date DATE
DATE=[1/2/2015]+5        #DATE = [06/02/2015]
DATE=[1/2/2015]-1        #DATE = [31/01/2015]

An example:

Local date LASTDATE
LASTDATE = eomonth([1/2/2015])
Infbox num$(LASTDATE)           #will display the date [28/02/2015]

To obtain a date as a string with a determined format:

format$("D:YYYYMMDD[_]hhmmss",date$)   

December 31, 2018 at 12.30 and 56 seconds will correspond to “20181231_123056”.

Note that square brackets are used to insert a space or other constant elements:
FORMAT = "DD[ ]MM[ ]YY"

To get the date and time as a formatted string, you can also use AFNC.FDH.
With this call it uses the formatting contained in the global variable GFMDAT.
Suppose that today is January 19, 2018, and GFMDAT contains “DD [/] MM [/] YY”

func AFNC.FDH(date$,"121531")          # restituisce "19/01/18 12:15:31"
func AFNC.FDH(date$,"")                # returns "19/01/18 17:08:27"
func AFNC.FDH(date$,"15:32")           # returns "19/01/18 15:32:00"
func AFNC.FDH(date$,"15")              # returns "19/01/18 15:00:00"
func AFNC.FDH(date$,"15:")             # returns "19/01/18 15:00:00"
func AFNC.FDH(date$,"error-string")    # returns "19/01/18         "
func AFNC.FDH(date$+1,"x")             # returns "20/01/18         "

It should be remembered that there are several global variables containing formatting strings,
all preset according to the predefined parameters.
They are useful to maintain a standard that adapts according to various users, sites, etc.

The order day-month-year of these formats depends exactly on the location and user settings.

The variables are these:

GFMDAT = standard date, with 2 caratteri for the day, 2 for the month , 2 for the year
GFMDAT4 = date with year of 4-digit
GFMDAT3 = date with month of 3 letters
GFMDAT9 = date with month written in letters
GFMMOI = month-year
GFMMOI4 = month-year with year of 4-digit
GFMJOU = day-month

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

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

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