Syntaxes used to define the name of a folder @ L.V. Expertise X3

Syntaxes used to define the name of a folder

When another folder is referenced, for example for copy or comparison operations, it is possible to use the following syntaxes :

FOLDER (the name of the direct folder : in this case, the folder is supposed to be directly accessible on the same server and the same service).
server@FOLDER (the network name for the server where the folder is located should be given : An adxd service must work on the current service number to allow the connection).
server:service@FOLDER (same principle as above, but the service number can be different. This gives, for example, the syntax server_01:1802@DEMO).

Important notes for copies

Warning: the last two syntaxes assume that there exists on the remote server a folder having the same name as the folder from where the function is run (even if it is not in this folder that the operation will be launched).

If the copy is made in a folder of the same type (for example from an X3 type to another X3 type folder), this condition is always filled when starting from the supervisor folder (X3 in the current case), because every installation of Adonix technology software assumes that a supervisor folder will as a minimum, be installed on the servers where the folders are located. It is therefore advisable to use the copy from the supervisor folder (X3 if it is ADONIX X3) in this case: It is in fact perfectly possible to copy an element from a folder that is not the current folder (even if the current folder is proposed by default), to another folder that is also not the current folder.

If the copy is made between two different software programs from the ADONIX family (e.g. Adonix X3, Warehousing GX, Abel X3, Adonix RH) this condition is not met. It is then recommended to reference the folders that should be copied using the link definition tab of the folder record.

In addition, when a process is associated with a dictionary element to be copied, this process is not copied. It will be necessary to carry it out manually. In the same way, the dictionary elements such as a data type, an activity code etc... defined in the element to be copied, are not copied.

Finally, when the copy operations lead to validations (code generations), they are not in general carried out when the target folder is on a different folder. It is better to pass by dictionary validations in the target folder.

Generic messages

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

server:sercice : Machine cannot be accessed

server : Machine canot accessed

The server that has been identified through it network path or it IP address has not been found. According to the network configurations, entering an incorrect network name can trigger a long wait time after entry of the field (since the check on the existence of a server is made on the network, there can be delay in the order of one minute, sometimes several minutes before an error message is received).