Kbase P25196: RoundTable. Deleted tables/fields cannot be added again to
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/15/2003 |
|
Status: Unverified
FACT(s) (Environment):
Roundtable 9.1x
FACT(s) (Environment):
Dynamics 2.0A
SYMPTOM(s):
RoundTable. Deleted tables/fields cannot be added again to the database
CAUSE:
Deleted tables/fields cannot be added again to the database.
If you have the following situation:
-In a version 1 of my Db there is a field called:
cmt_sad.declaration_vat_no.
-This field is also deployed to another site/workspace.
-In a next db-version this field was dropped.
During load-schema RTB asks to delete the object from the RTB repository. Answered: YES. Also removed from Dynamics repository(as adviced).
-This is also deployed.
-In next db version, this field is added to the DB and we do a load schema in RTB.
During load schema, the system prompts that there is already an object
with same name and I have to choose another objectname. So you enter: cmt_sad.declaration_vat_no_2
-Then if you run an entity import on that table.
That gives the error:
Attempt to create data corresponding to an object named cmt_sad.declarant_vat_no which is not checked out in the SCM tool under workspace 100CM2-DEV. (RV:27)
FIX:
This is a Roundtable issue that comes about as a result of the design of Roundtable. It does not have anything to do with the integration between RTB and Dynamics.
There is 2 ways of working with RTB to correctly handle this situation:
1. Before doing a schema load, the fields that are being re-added must be manually assigned to the workspace and an update schema with the SKIP option has to be done. When the schema load is done, the field will then automatically
be checked out and updated by RTB.
2. The other option is not to delete the fields (PFIELD objects) as they become redundant but leave them in RTB. This means that the extra step of assigning the object back to RTB can be avoided. However, it leaves a number of objects
in the workspace that are redundant. This does not have any affect on RTB or any adverse side effects - apart from the extra unused objects in the workspace.
It have been discussed the possibility of making this easier for the users of RTB in the future with the RTB development team.
Improvements to the schema management are already planned and will be included as early as possible in one of the coming releases.