CST-334: Fix case entity not being imported #970
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olayiwola-compucorp
changed the title
This error happened because the getvalue endpoint expects the return param to be a string type and not an array
olayiwola-compucorp
force-pushed
the
CST-334-fix-case-import
branch
from
e53206e
to
0f64ddd
Compare
omarabuhussein
approved these changes
Sep 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR fixes an issue in the extension that prevents the case entity from being imported using the
CSV importextensionBefore
Import hangs and the error below is thrown
After
Import is successfully completed
Technical Details
This error happened because the
CaseType.getvalueendpoint expects the return param to be a string type and not an array