You are viewing this site as a guest. You can still ask questions and help others! Join our Dev2Dev IT Community to receive your own blog, share your knowledge, and much more.

How to migrate a record w/o migrating the field definitions

6 replies [Last post]
Guest's picture
Guest

Compshack,

I have a interesting scenario.

I have a record with say 10 fields, of which 6 are custom fields and 4 are delivered fields.

The delivered fields also exist in the target data base where I want to migrate the record.

However, I want to make sure that only the record definition gets migrated and not the fields.
I am asking this question as a continuation of my previous question.

I am not even sure of what to expect . I noticed that when I migrated the record (just the record ), the 4 custom fields ended up being created. I am not so sure whether the delivered fields got overwritten.
My issue is that there could be problems with the delivered fields on the source database that I do not want t be pushed to the target database at any cost.

Also, at this time, I do notwant to make changes to the record in the source database as I have been told to preserve its state in the source database.

Any suggestions ?

CompShack's picture
User offline. Last seen 6 years 4 weeks ago. Offline
Joined: 12/09/2007
Posts: 167
Re: How to migrate a record w/o migrating the field definitions

When you insert a record into a project, only the record will get migrated unless you inserted "related definitions" for that record. Fields on a record are considered related definitions. Before you migrate, check your upgrade tab to make sure no fields are in your project.

To make sure related definitions don't get inserted into your project automatically, go to Tools > Options. On the project tab, choose "Prompt user to pick related definitions to insert" and under Insert Definitions into Project, choose Manually.

Open your record in application designer, hit F7 and choose no related definitions if you only want the record to be migrated and nothing else then click Ok.

If you follow the steps above, your fields shouldn't get migrated, unless of course you added them to the project.

Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog

HH's picture
HH (not verified)
Re: How to migrate a record w/o migrating the field definitions

Thanks you!

The problem still persists.

The fields were not included in the upgrade tab.

However, I inserted record using insert definitions into project and specifically selected 'RECORD'. and did not select any related definitions to insert.

In the Options > Project, I selected "Ask before inserting related definitions" so that i have control over which related definition I want to be included. ( I have this setting from the beginning. )

I also tried the other method to insert a definition. Open the record ( after creating a new one ) and hit f7.

When I hit f7, it specifically asked me which related definitions to include in the project and I did not select any related definition to migrate.

I did not see any fields included in the upgrade tab. Only the record that I inserted.

After migrating the record, I see the field definition migrated as well.
Hmm..

Is it a bug ?

If there is no way out, I will have to create about 500 records/views manually. Not a very good position to be in.

CompShack's picture
User offline. Last seen 6 years 4 weeks ago. Offline
Joined: 12/09/2007
Posts: 167
Re: How to migrate a record w/o migrating the field definitions

Don't know why that is happening. When you move a record from one environment to another, fields will not get migrated unless you specify you want them to.

If however you moved a record that has fields f1, f2 and f3 and f1 and f2 are already in your target environment then your record will have f1 and f2 on it automatically. f3 will not show on your record as it never existed in the target database to start with. This is how it is on the current version we are on (8.12) - I wouldn't know if this is different in PS8.49, never used it to migrate objects!

Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog

HH's picture
HH (not verified)
Re: How to migrate a record w/o migrating the field definitions

I have a confirmation that this does happen. Missing fields get migrated. But not all the properties.

I hope that that does not happen with pages :)

Ashar's picture
User offline. Last seen 4 years 34 weeks ago. Offline
Joined: 03/26/2008
Posts: 227
Re: How to migrate a record w/o migrating the field definitions

once u run the compare report, missing fields will automatically be included in the upgrade.
you wud have to uncheck the upgrade check box manually if u dont want it to be migrated..
but i'm not sure why you dont want the missing fields to be migrated.

HH's picture
HH (not verified)
Re: How to migrate a record w/o migrating the field definitions

We have upgrade to v9 as is w/o much analysis. And now want to selectively move customization to our development env.

We see the old version delivered fields that have now been dropped by P/S but still persist in the 'upgraded' db.
Our plan is to replace those with an existing delivered field. Or create a custom field. ( instead of using