Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration Migration Tool User Mapping and pac data Import #705

Closed
eleung83 opened this issue Sep 16, 2023 · 1 comment
Closed

Configuration Migration Tool User Mapping and pac data Import #705

eleung83 opened this issue Sep 16, 2023 · 1 comment

Comments

@eleung83
Copy link

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?

@petrochuk
Copy link
Contributor

Converting to discussion so it can be voted on

@microsoft microsoft locked and limited conversation to collaborators Sep 17, 2023
@petrochuk petrochuk converted this issue into discussion #708 Sep 17, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants