Kbase P14340: Dynamics and calculated field
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.0a
SYMPTOM(s):
Unable to use a calculated field in dynamic sdo
FIX:
When calculated fields are defined for Dynamic SDOs, they don't work. The problem is because
there is no place in a Dynamic SDO to put the code for the calculated field. The code must go
into the Data Logic Procedure.
Currently a Dynamic SDO and its associated DLP are considered 2 separate objects by the
AppBuilder. That is, when you open the SDO, only it is open. When you save the DynSDO only
it is saved. Similarly, when a DLP is opened, only it is opened and when the DLP is saved only
it is saved.
This will need to change in order to support Calculated fields. Here is what will happen:
1) DLPs will still be opened, editted, saved and closed independently of their associated SDO.
2) When a SDO (either dynamic or static) is opened, its associated DLP (if it exists) will also be
opened simulataneously. However, the AppBuilder will still view them as 2 separate objects
with one exception (#3 below.)
3) When a calculated field is defined for an SDO, the code will become part of DATA.CALCULATE
in the associated DLP.
4) If a static SDO doesn't have an associated DLP then DATA.CALCULATE will be saved in the
static SDO as has been historically done.
5) If a dynamic SDO doesn't have an associated DLP, then the calculated field button will be
grayed out and it won't be posible to create a calculated field for that SDO.
6) If the user has closed the associated DLP when attempting to create or edit Calculated
Fields, an error message will appear when attempting to save the SDO telling the user that
changes to DATA.CALCULATE will not be saved.