[Bug] Throwing error while importing the json file

[maruthasalamr]

Bug report while importing the json file - Missing message: strapi-import-export.plugin.form.field.id-field.placeholder for locale en , using id as fallback.

Node Version - v18.20.2
Strapi version - 5.0.0
strapi-import-export - 0.0.1
Database - PostgresSQL
Operation system - Mac Os

[Moonlight63]

I also got this one. It doesn't really matter because its just saying that the localization string is missing from the translation files, but I did fix it in my fork when I added the new export format. You can install it if you want: https://www.npmjs.com/package/strapi-import-export-v3?activeTab=readme

[gorgsenegger]

Apart from the error message that I also receive, the import just doesn't work in v5.8.0 - no error message in the UI or console though, so I don't know what the problem is.

[Moonlight63]

Apart from the error message that I also receive, the import just doesn't work in v5.8.0 - no error message in the UI or console though, so I don't know what the problem is.

I know it sounds stupid, but does the data show up if you refresh the page? This is something I found even in my new version, that after the data imports even though we tell the list to refresh, the new data doesn't show up until the full page is refreshed. I haven't figured out why yet.

[gorgsenegger]

I know it sounds stupid, but does the data show up if you refresh the page? This is something I found even in my new version, that after the data imports even though we tell the list to refresh, the new data doesn't show up until the full page is refreshed. I haven't figured out why yet.

Thanks for the suggestion, unfortunately that didn't work for me :-/

Did you update with a file or did you paste the file contents by selecting "Code Editor" after pressing the import button? Do you have an example of what your json (if used) looks like? I tried updating a single entry in one of my collections, so nothing too complicated.

[Moonlight63]

I typically used the code editor and pasted in but I did try the file selector a few times just to make sure it works. I should clarify that I haven't tried this version of the plugin on 5.8, only my v3 fork, which has a completely different json structure. I've been testing it for a bit making sure its good before submitting a pull request, but it hasn't given me many issues so far except for localizations aren't working great, but that has more to do with the way strapi works than anything. Ill submit a pull request for it here now, and maybe I can fix localizations in a v4 or something.

[GraemeFulton]

Hey I'll give this a go too - should get chance either today or early next week!

[Przecza]

I have issues with updating during import (by API). Creating is good. There is a wrong ID used In updateOrCreateCollectionTypeEntry function. In update if/else:

return strapi.documents(slug).update({
  documentId: dbEntry.id,
  data: omit(fileEntry, ['id'])
});

should be dbEntry.documentId, not dbEntry.id

Create branch works good enough for me.

Will try to do PR.

[maruthasalamr]

@Przecza issue is fixed ?

[maruthasalamr]

Hi @Moonlight63 i got the issues while importing the content
https://www.npmjs.com/package/strapi-import-export-v3?activeTab=readme

This is my schema.json ` "pluginOptions": { "i18n": { "localized": true }, "strapi-import-export": { "idField": "customField" } }, "attributes": { "customField": { "type": "string", "required": true, "unique": true }, "name": { "type": "string", "required": true, "pluginOptions": { "i18n": { "localized": true } } } } `

[Moonlight63]

Yeah, it's telling you the issue. The "customField" field is missing from your import data. (Also website_locale it looks like). If a field is set to required in your schema, then it is required in your import data. The assumption is that you are exporting the data from the same or similar source, so a required field would exist.

[Moonlight63]

Also FYI, a known issue I haven't fixed yet, if you try to import a big dataset, the connection will likely timeout. Strapi admin treats this like an error, but in the background it may still be importing. So something to keep in mind. I need to figure out how to change the way things report and do a websocket or sse or something. But that hasn't come up enough for me to bother. Mainly happens when importing something with media.

[Przecza]

@Przecza issue is fixed ?

The PR is there for a while:
https://github.com/Prototypr/strapi-import-export/pull/5/files. My use case is fixed by this. I am not sure who can merge it.

[Moonlight63]

I made some updates to my import v3 fork as well that fixes some things like refreshing the data in the admin panel when importing is complete and handling really large imports using SSE so the connection doesn't time out. Probably going do another rewrite of the import system (again) now that I have a better grasp on how strapi actually works under the hood.