You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did create a data export in my production instance of Structr and am trying now to import this into my development instance.
For the import, I am using the API /maintenance/deployData/.
Structr version is 5.3-SNAPSHOT.
Within the target instance, I do get the following errors
Unable to import nodes for type Group
FrameworkException(422): Unable to commit transaction, validation failed ErrorTokens: Group.name already_taken d0d041dfffb5426cbadbd071dd4a48e2. Existing uuid: 829797c7edf642f6943c7dd2e9c1ce69
Unable to import nodes for type SchemaGrant
FrameworkException(422): Unable to commit transaction, validation failed ErrorTokens: SchemaGrant already_taken d0796c60aa834a188cdbf4d49a629057
Unable to import nodes for type SchemaNode
FrameworkException(422): Unable to commit transaction, validation failed ErrorTokens: SchemaNode.name already_taken 96796183edb546fcb5bae837e0b700a5. Existing uuid: d1ef8ee09d8840c5a5d07c0ac5e63f9f
Unable to import nodes for type SchemaRelationshipNode
FrameworkException(422): Unable to commit transaction, validation failed ErrorTokens: SchemaRelationshipNode.sourceNode must_not_be_empty, SchemaRelationshipNode.targetNode must_not_be_empty
Prior the data import, I did a schema import through /maintenance/deploy/ which went all fine.
How can I accomodate those errors?
The text was updated successfully, but these errors were encountered:
preske87
changed the title
Importing data from other structr instance results in FraemworkException
Importing data from other structr instance results in FrameworkException
Oct 17, 2022
From the looks of these messages, the set of exported types contains built-in types. This is only in rare cases necessary.
These built-in schema nodes/grants/relationships are all included in the regular deployment export and should already be present after a deployment import.
Users already raise a warning, that this can lead to problems (usually if the currently logged in user is in the data deployment import).
Exporting groups probably results in a huge export folder with relationships (which should already be created by regular deployment).
I did create a data export in my production instance of Structr and am trying now to import this into my development instance.
For the import, I am using the API
/maintenance/deployData/
.Structr version is
5.3-SNAPSHOT
.Within the target instance, I do get the following errors
Prior the data import, I did a schema import through
/maintenance/deploy/
which went all fine.How can I accomodate those errors?
The text was updated successfully, but these errors were encountered: