Each of these 4 files have the same iud in common.
However, this does create 4 documents in the 4 locales, but they are not linked together. In other words, when I enter the French version and switch to the English version, there is nothing (no alternate language on the API). Each document is independent. I would like to be able to import them and have them linked together.
Here is an example of a json file:
{
"uid": "V829V-1376",
"title": [
{
"type": "heading1",
"content":
{
"text": "Michael Mokassins",
"spans":
}
}
],
"description_full": [
{
"type": "paragraph",
"content":
{
"text": "Die Michael Mokassins, eine 2009 ins Leben gerufene Hommage an den König des Dancefloor Michael Jackson, gehören zu den ikonischen Produkten des Hauses",
"spans":
}
}
],
"type": "product_post",
"lang": "de-de"
To translate content in different locales, you need to create a document in the master locale in the Prismic editor. And then export the document to retrieve grouplang id.
Next, prepare your translation file with this naming convention: translate_grouplang_lang.json.
The following article describes the feature importing new content in multiple languages is not working the way it should work. It does import documents, but they are not connected. Documents are imported as independent content.
For the moment, the workaround I suggested above is the way.
I have reported this to our product team and will update you as I hear back from them.
We've just updated the article you're referring to so that this method can be used again: the arbitrary "groupid" used in the file naming convention needs to be a 16 characters id, this info was missing on this article.