Open KestasVenslauskas opened 1 year ago
Here is the PR to fix it:
EDIT: but this works only for 2 locales max. I but as I see import v2 did not worked with more than 2 locales even before
@Baboo7 We tested this fix and can confirm that it works as expected. Waiting for your approval and a new release :)
@Baboo7 why is this being ignored?
Describe the bug For non-default locale imported models ID's are different.
Here is the exported json v2:
I created test model with 2 fields 'title' & 'subtitle'
Steps to reproduce the behavior:
Expected behavior All id's are the same as in the JSON v2.
Actual result The IDs of entries in non-default locale are incremented. If I delete / import again all EN (default) locale IDs will remain the same but will be incremented on LT (secondary) locale.
Additional context The biggest problem is when we have nested contentTypes and import gives errors because IDs does not match saying "1 relation(s) of type api::some-type.some-type associated with this entity do not exist"