Skip to content
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

Error when original guid does not exist in the source file for mapped reference field #19

Closed
ksulikow opened this issue Nov 11, 2020 · 0 comments · Fixed by #20
Closed
Assignees
Labels
bug Something isn't working

Comments

@ksulikow
Copy link
Contributor

Describe the bug
When export config contains fields mappings defined, but has the reference field excluded from export, the original guid will not be included in the exported data. It will cause error and fail during import.

To Reproduce
Create export config file and configure lookup mapping and add the field to excluded fields
"ExcludedFields": [
"systemuserid",
"roleid",
"systemuserrolesid",
"businessunitid"
],
"LookupMapping": {
"systemuser": {
"systemuserid": [
"domainname"
],
"businessunitid": [
"name"
]
},
"systemuserroles": {
"systemuserid": [
"domainname"
],
"roleid": [
"name",
"businessunitid"
]
}
}

Expected behavior
In this situation if lookup value can be found in the target system then it should be used, if not it should be left empty

Additional context
Fatal error during import

@ksulikow ksulikow added the bug Something isn't working label Nov 11, 2020
@ksulikow ksulikow self-assigned this Nov 11, 2020
ksulikow added a commit that referenced this issue Nov 11, 2020
@ksulikow ksulikow mentioned this issue Nov 11, 2020
@ksulikow ksulikow linked a pull request Nov 11, 2020 that will close this issue
ksulikow added a commit that referenced this issue Nov 11, 2020
markcunninghamuk pushed a commit that referenced this issue Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant