Rules and guidelines

• •The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:

Transformations	Object Type	Advanced Fields
Source	Single object	Folder path and file name
Lookup	Single object
Target	Single object

• •After you migrate the mapping from Org1 to Org2, you must not edit the mapping.
• •For an existing target object in Org2, you must specify the folder path and file name in the advanced properties. If the object does not exist in Org2 or the connection does not have access to the object that you used in Org1, the mapping fails with a 403 error.
• •Ensure that you specify a valid folder and file name in the advanced properties. Otherwise, the mapping fails.
• •When you use the FileName field in a target object, override the folder path and file name, and migrate the mapping to Org2, the mapping fails with a 403 error. This issue occurs if the connection in Org2 does not have access to the bucket, object, and folder path that you used in Org1.
• •When you specify wildcard characters in the folder path advanced property, all folders that match the name pattern must contain files with the same metadata and formatting options.
• •When you recursively read files from subdirectories, the folder path advanced property that you override must contain a file in the directory.
For example, if you specify the folder path as <bucket1>/<dir1>, ensure that a file is present in the directory, <dir1>: <bucket1>/<dir1>/<file1>.
If the folder path advanced property contains files only in the subdirectories and no file in the directory, the mapping fails.
• •You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides as schema change handling is not supported.
• •You can configure all encryption types, except Informatica encryption, in a mapping that you migrate to the new environment.
• •When you select the source type as Directory, delete any auto-generated transactional files, for example, .tmp, for the mapping to run successfully. The _SUCCESS and .CRC files are ignored.
• •If you do not provide the bucket name and specify the folder path in the advanced property starting with a slash (/) in the /<folder_name> format, the folder path appends with the folder path that you specified in the connection properties.
For example, if you specify the /<dir2> folder path in the advanced property and <my_bucket1>/<dir1> folder path in the connection property, the folder path appends with the folder path that you specified in the connection properties in the <my_bucket1>/<dir1>/<dir2> format.
If you specify the <my_bucket1>/<dir1> folder path in the connection property and <my_bucket2>/<dir2> folder path in the advanced property, the Secure Agent writes the file in the <my_bucket2>/<dir2> folder path.
• •Ensure that you specify a valid override folder path in the advanced properties for a mapping in advanced mode. If the override folder path pattern does not match with the actual folder path, the mapping fails.
• •When the source object is enabled for recursive read in the mapping, after the migration, make sure you have a file in the parent directory in the overridden folder path specified for the source object, or manually reselect the object. Otherwise, the mapping fails.