Kbase P185554: ADM2: getLogicalObjectName returns blank for Simple SmartObject if the LogicalObjectName is set at
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/8/2011 |
|
Status: Unverified
SYMPTOM(s):
ADM2: getLogicalObjectName returns blank for Simple SmartObject if the LogicalObjectName is set at design time.
The LogicalObjectName property of a Simple SmartObject set via its 'Instance Properties' is reset to blank when the Simple SmartObject is saved.
The LogicalObjectName property of a Simple SmartObject set via its 'Instance Properties' at design time displays as a blank value at runtime.
Invoking the getLogicalObjectName function, using a call similar to the following, returns a blank value for the Simple SmartObject LogicalObjectName property even though it is set to a non blank value at design time:
DYNAMIC-FUNCTION('getLogicalObjectName' IN THIS-PROCEDURE).
FACT(s) (Environment):
Windows
Progress 9.1x
OpenEdge 10.x
OpenEdge Category: Language (4GL/ABL)
CAUSE:
Bug# OE00109385
FIX:
This is a limitation in the AppBuilder. The LogicalObjectName property is set only in a Dynamics environment. It cannot be set at design time in ADM2 environment using the AppBuilder. A workaround is to set the LogicalObjectName property in an initializeObject procedure override of the Simple SmartObject using the 'setLogicalObjectName' function. For example, execute the following statement before or after the RUN SUPER statement of the Simple SmartObjectinitializeObject procedure:
DYNAMIC-FUNCTION('setLogicalObjectName' IN THIS-PROCEDURE, "cLogicalObjectName":U).