Kbase P121752: Dynamics getSessionResultCodes does not work on AppServer Runtime session.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/24/2007 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics
SYMPTOM(s):
Dynamics getSessionResultCodes does not work on AppServer Runtime session.
Customization result codes cannot be retrieved with 'getSessionResultCodes' on a Dynamics Runtime AppServer session.
The customization Manager function ''getSessionResultCodes' works in thick client server sessions.
getSessionResultCodes only returns DEFAULT-RESULT-CODE in the AppServer Runtime session.
CAUSE:
The getSessionResultCodes API should not be used to retrieve client customization on the server.
FIX:
Use the getClientResultCodes() API instead of getSessionResultCodes.
Each session has its own result codes. Each client session has one set, and the AppServer has its own. The Result codes on the server are not used for anything, but since an AppServer is a normal session type, the result codes are set.
The getSessionResultCodes() API will return the result codes for the current session, so in an AppServer session will typically return DEFAULT-RESULT-CODE.
The client's result codes are stored in context and are accessible from the server. getClientResultCodes() in the CustomizationManager returns the result codes for the client session when called on the AppServer, and the current session's result codes when called on the client. This API can (and should) thus be used to determine the current client's result codes.