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

ISSUE-106: Fix "not keeping old RELS" #107

Merged
merged 1 commit into from
Feb 17, 2020
Merged

ISSUE-106: Fix "not keeping old RELS" #107

merged 1 commit into from
Feb 17, 2020

Conversation

DiegoPino
Copy link
Contributor

What is the issue?

See #106

There was plenty wrong here when telling IMI to keep existing RELS-EXT relationships in place:
1.- We were forcing a new RELST-EXT datastream to be created in the batch object by adding the CMODEL
2.- We were opening to door to IMI's getDatastreamsforUpdate to take new RELS EXT in consideration.

What is new?

This unsets any existing RESL datastreams and also only adds CMODEL to the other Update modes.

There was plenty wrong here when telling IMI to keep existing RELS-EXT relationships in place:
1.- We were forcing a new RELST-EXT datastream to be created in the batch object by adding the CMODEL
2.- We were opening to door to IMI's getDatastreamsforUpdate to take new RELS EXT in consideration. This unsets any existing RESL datastreams and also only adds CMODEL to the other Update modes.
@DiegoPino DiegoPino added the bug label Sep 17, 2019
@DiegoPino DiegoPino merged commit 4c48f58 into master Feb 17, 2020
@DiegoPino DiegoPino deleted the ISSUE-106 branch February 17, 2020 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant