A record field reference within a project includes a field name. Line two in the preceding image is a record field reference.
Compares are useful for preparing a migration, but should be run at the appropriate time and under the appropriate circumstances. Here are some principles to keep in mind when comparing a project with records in it:
Record field changes do not show up in compare reports. “Compare report” refers to the diff file that shows up in Application Designer, like this:
With those principles in mind, the following scenarios will all result in a record in the target environment with only the RMT1 field in it having the RMT2 field added to it after it has been added in the source environment:
The following scenarios will result in the RMT2 field being removed from the record in the target environment when it has been removed from the source environment:
Here are other copying principles to keep in mind:
Using the CopyProp action does not copy a record definition or record fields. The "Copy" action copies record properties, as well as all of the source database’s record fields, but CopyProp copies only the record properties. In that case, any desired record field changes must be handled individually through project record field references.In the four scenarios below, the first two would result in the removal of an extra RMT2 field in the target database, while the last two would not.
That's it! Good luck migrating your records
Written by Bryan K. Elkins, Technical Manager
Copyright (c) 2016 Gideon Taylor Consulting, All Rights Reserved.