List of possible issues and solutions
Risk or error message |
Explanation and possible solution |
The script $1$ that exists in the application $2$ should not be in $3$ |
A standard script has been placed in a child folder. Delete the standard script and apply the needed customizations through object or field actions, or entry points. |
A specific activity code must be >=X |
Specific activity codes must start with X, Y, or Z. |
the maximum dimension has been modified from $1$ to $2$ |
A standard screen dimension has been changed. This can be overwritten when a standard screen is contained in an update and exposes you to issues due to standard code. Use dimension activity codes instead. |
This specific table is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific table is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The standard activity code $1$ has been replaced by the specific activity code $2$ |
A standard activity code was replaced. Use activity code dependencies instead. |
The specific activity code $1$ has been assigned to this standard table |
A standard table was protected using a specific activity code. This can cause the table to miss an update if it is contained in a future standard patch. Make sure you check whether this table is included in future updates and take the necessary actions to allow it to be updated. |
It is prohibited to add a specific column ($1$ - $2$) in a dictionary table. |
You cannot add specific elements to supervisor or dictionary tables. This can cause the system to function improperly or crash. |
The specific column $1$ ($2$) is not protected by an activity code |
You have added a specific field in a standard table. It needs to be protected with a specific activity code. Unprotected fields can be lost during an update or when validating a folder. |
The local menu $1$ has been deleted |
A standard local menu has been deleted. This can cause the system to malfunction or crash. |
The local menu $1$ has been replaced by menu $2$ |
A local menu was replaced in a dictionary definition. They can cause the system to crash or malfunction. |
The standard length ($1$) has been reduced to $2$ |
Reducing lengths of standard fields or data types can cause the system to malfunction or crash. Never reduce the lengths of standard elements. |
The standard length ($1$) has been increased to $2$ |
Increasing the lengths of standard elements can cause inconsistency or data loss. |
This specific data type is not protected by an activity code |
A specific element was not protected. It can be lost when updating, upgrading, or validating the folder. |
This specific data type is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The internal type ($1$) has been replaced by $2$ |
Replacing internal types is dangerous and can cause inconsistencies and data loss. |
This specific miscellaneous table does not exist in the reference folder and is not protected by an activity code. |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
Property ($1$) has been modified but the activity code is not entered |
A standard element was modified but not protected. It can be lost when updating, upgrading, or validating the folder. |
This specific local menu does not exist in the reference folder and is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific screen is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific screen is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The specific activity code $1$ has been assigned to this standard screen |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
The standard block no $1$ ($2$) has been moved or deleted |
A standard screen block was moved or deleted. You should never move or delete standard screen blocks because they can be referenced by standard scripts. This will cause malfunctions and/or data loss. |
The type of the standard block no. $1$ ($2$) has been modified for $3$. |
A standard screen block was modified structurally. This will cause malfunction, fatal errors, and/or data loss. |
The rank of the standard block no. $1$ ($2$) has been modified from $3$ to $4$. |
A standard block rank was changed. You should never change block ranks because they can be referenced by standard scripts. This will cause malfunctions and/or data loss. |
The activity code of the standard block no. $1$ has been replaced by the specific activity code $2$. |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
The specific block no. $1$ ($2$) has been added without being protected by an activity code. |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
The specific field $1$ ($2$) is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific window is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific window is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The specific activity code $1$ has been assigned to this standard window |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
The rank of the standard tab no. $1$ ($2$) has been modified from $3$ to $4$. |
A standard tab rank was changed. You should never change tab ranks because this can cause updates to malfunction. |
This specific action is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific action is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The specific activity code $1$ has been assigned to this standard action |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
This specific class is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific class is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The specific activity code $1$ has been assigned to this standard class |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
It is prohibited to add a specific collection ($1$ - $2$) to a class $3$. |
You cannot add a specific collection to this class. |
The specific property $1$ ($2$) is not protected by an activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
The specific activity code $1$ has been assigned to this mandatory standard property |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
This specific representation is not protected by a standard activity code |
A specific element has not been protected. It can be lost when updating, upgrading, or validating the folder. |
This specific representation is protected by a standard activity code |
A specific element is protected by a standard activity code. Replace the activity code with a specific activity code. |
The specific activity code $1$ has been assigned to this standard representation |
A standard element was protected using a specific activity code. This can cause the element to miss an update if it is contained in a future standard patch. Make sure you check whether this element is included in future updates and take the necessary actions to allow it to be updated. |
Specific development not allowed for an object of the Supervisor" module." |
You cannot customize supervisor objects. This can cause the application to malfunction. |
After the addition of an action, the parameters must be entered in the screen dictionary |
An action that does not have parameter values was detected. Make sure you enter values for the action's parameters in the screen definition. The Control menu in the screen dictionary provides the list of the screens impacted by this modification. |
This screen does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This table does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This window does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This action does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
The specific activity code $1$ has been assigned to this standard data type |
Adding specific actions to standard data types can cause malfunctions if the specific action restricts data controls in any way. Make sure your action is not disruptive, or duplicate the standard data type into a new one. |
The standard activity code $1$ has been deleted |
Never delete a standard activity code. This will cause malfunctions and/or data loss. |
This data type does not exist in the reference folder and does not comply with standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This class does not exist in the reference folder and does not comply with standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This representation does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
The data type $1$ has been replaced by $2$ with an internal type reducing field length |
Reducing the length of a data type will cause malfunction or data loss since standard elements in the system rely on a minimum data length. |
The data type $1$ has been replaced by $2$ with an incompatible internal type |
Incompatible internal types will cause the data type to malfunction. Make sure the internal type is consistent with the actual data type (alphanumeric for alphanumeric values, numeric for numbers, and so on). |
This miscellaneous table does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
This local menu does not exist in the reference folder and does not comply with naming standards |
An element that seems specific does not start with X, Y, or Z. All specific elements must be named using X, Y, or Z prefixes. |
The $1$ field in the $2$ screen belongs to the $3$ block which no longer exists. |
A field belongs to a nonexistent block. Move the field to a new block. |