Kbase P98055: Adding a new calculated field to a Smart Data Object gives an error on save.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0B
Roundtable
SYMPTOM(s):
Adding a new calculated field to a Smart Data Object gives an error on save:
Check-out failed - trying to modify object in non-primary workspace, object: arm_customer.ado
The ADO-file mentioned in the error message corresponds to the Entity Object of the Smart Data Object table
The Roundtable Product Module of the Smart Data Object table entity object is not primary for the current Workspace
CAUSE:
Open Edge Dynamics 10.0B manages in different way the calculated fields so they can be reused: Every time you use a calculated field in a SmartDataObject, a note will be written in the SmartDataObject table entity object. Because of this Roundtable will try to check out the SDO table entity object in the current Workspace which will give an error message if the Product Module of the SDO table entity object is not primary.
FIX:
Create a Custom Variant of the SDO table entity object, so it's Product Module will be primary for the current workspace.