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

Misleading error if import returns no docType #3389

Closed
matthias-ronge opened this issue Apr 3, 2020 · 0 comments · Fixed by #4906
Closed

Misleading error if import returns no docType #3389

matthias-ronge opened this issue Apr 3, 2020 · 0 comments · Fixed by #4906
Labels

Comments

@matthias-ronge
Copy link
Collaborator

If import returns a field docType, but the ruleset does not know any field docType, then the field is displayed with yellow marking and no error message appears. (So it is correct.) However, if import does not return a field docType, then an error message says that there is no field docType in the rule set.

Goal: Clarify error message that error is in import XSLT, not tin the ruleset.

@matthias-ronge matthias-ronge changed the title Misleading error message if import has no docType Misleading error if import returns no docType Apr 3, 2020
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 a pull request may close this issue.

1 participant