Importer Pivoted Source Type can hide bugs
#2224
Comments
soininen
added a commit
to spine-tools/Spine-Database-API
that referenced
this issue
Aug 9, 2023
Import mappings should ignore the position of last mapping if the mappings are pivoted. This did not happen, however, when one of the other mappings was marked as header and there were no explicitly set pivoted mappings. We now take this special case into account. Re spine-tools/Spine-Toolbox#2224
soininen
added a commit
to spine-tools/Spine-Database-API
that referenced
this issue
Aug 9, 2023
Mappings are not pivoted when only the leaf mapping has position set to header. Re spine-tools/Spine-Toolbox#2224
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Importer seems to have a bug where the
PivotedSource Typeis displayed, but in actuality something else is saved in the importer specification. I had managed to create a situation where the importer specification editor displayed the following:However, in reality, the importer specification .json had the following:
resulting in nonsense being imported into the DataStore.
I couldn't seem to figure out a way to see or change this error through the import specification editor in toolbox, as it refused to display the parameter value field as anything besides
Pivoted.I'm not sure how I managed to create this bug in the first place, but I imagine I could have accidentally entered
Headerin the Parameter Values field first when creating the original specification, before entering it a second time into the correct Parameter Names field.The text was updated successfully, but these errors were encountered: