You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Configuration Migration Tool to build a data schema for the the import and export of data, one is also allowed to provide a User mapping file during the import process if their data schema contains user records.
Yet, if I attempt to perform the same actions using the pac cli commands to perform the same import and export functions ("pac data export" and "pac data import"), there seems to be no way I can provide this user mapping file, which then renders me unable to auto export and import data from one environment to another which has some dependency on the user entity (for example teams).
Is there any way to somehow force the pac data import commands to accept a user mapping file?
The text was updated successfully, but these errors were encountered:
When using the Configuration Migration Tool to build a data schema for the the import and export of data, one is also allowed to provide a User mapping file during the import process if their data schema contains user records.
Yet, if I attempt to perform the same actions using the pac cli commands to perform the same import and export functions ("pac data export" and "pac data import"), there seems to be no way I can provide this user mapping file, which then renders me unable to auto export and import data from one environment to another which has some dependency on the user entity (for example teams).
Is there any way to somehow force the pac data import commands to accept a user mapping file?
The text was updated successfully, but these errors were encountered: