Hi,
I am migrating the new changes of dev chatbot to product chatbot in Dialogflow CX.
The way I do it is exporting all the intents of the dev chatbot and then import them in production chatbot. But I found that although it keeps the labelling of entity types in training phrases, the entity types I defined in dev chatbot are all gone.
How to prevent that from happening? Or am I doing it in the right way when applying changes from dev to prod?
Solved! Go to Solution.
I got some finding of the behavior when importing the entity type.
It seems it won't work for the entity types that have multiple entities.
For example, previously, I have entities "hotel A" and "hotel B" under the same entity type "hotel". And it won't work when I import an updated version.
Now I group them into a single entity "hotel" and then it works for me.
I export the entity types from dev chatbot and try to import them in prod chatbot. But an error "Internal error encountered." pops up without other hints.
It would be great if there's anyone who encountered similar situation can share your thoughts. Thank you in advance.
Hello,
Thank you for contacting Google Cloud Community!
Unfortunately, exporting intents in Dialogflow CX doesn't automatically include the associated entity types. These need to be migrated separately.
The "Internal error encountered" message during entity type import is not very informative. There could be several reasons behind this, but common causes include invalid entity type definitions or conflicts with existing entities in your production environment.
I hope this information was helpful.
Regards,
Jai Ade
Can I know more about the "invalid entity type definitions"?
I am uploading the entity type I exported from Production chatbot (in a zip file of JSON), and choose to replace the existing ones. But this is where I got the "Internal error encountered" message.
When I export all the intents, add new training phrases and then import the intent back to the same chatbot, it keeps the entity types after importing intent. And I can see the parameter labelling is still there in the training phrases.
However, if the entity type per se is used inside the training phrases, the content just becomes empty.
Hello,
The issue you're encountering with the "Internal error encountered" message when trying to replace entity types in your chatbot points towards a potential problem with the uploaded zip file or the replacement process itself. Here are some troubleshooting steps you can try:1. Ensure the zip file you're uploading is valid and doesn't contain any corrupted files. Try re-exporting the entity types from your production chatbot to get a fresh zip file.
2. Open the zip file and verify that the JSON files within it are well-formatted and contain valid entity type information. You can use a JSON validator online to check the format.
For more information on entities please refer [1].
If your issue is still not resolved ,you can contact the GCP support[2]
[1] https://cloud.google.com/dialogflow/cx/docs/concept/entity
[2] https://cloud.google.com/support/docs/manage-cases#creating_cases
Regards,
Jai Ade
Hello,
Thank you for your engagement regarding this issue. We haven’t heard back from you regarding this issue for sometime now. Hence, I'm going to close this issue which will no longer be monitored. However, if you have any new issues, Please don’t hesitate to create a new issue. We will be happy to assist you on the same.
Regards,
Jai Ade
Hi,
I am having issues importing intents and entities into a new bot. The file structures are directly from a previously exported bot, but it is still producing errors. When I go to upload a zip file titled : entityTypes.zip I get this issue
Then when i go to import intents from a file intents.zip i get this issue:
There is no csv, it has json files. Like i mentioned, the file structures from both intents and entityTypes are directly from an export of a previous bot, which makes me think there could be something else wrong. I couldn't find any guidelines on these issues, any idea?
For the issue on intent import, I encountered once and it seems it has something to do with the format or encoding of your csv file. Maybe you can export the source as csv and try to edit it in Excel.
For the entity type import error, I think you need to make sure that the 1st layer of your zip file is named "entityTypes".
I got some finding of the behavior when importing the entity type.
It seems it won't work for the entity types that have multiple entities.
For example, previously, I have entities "hotel A" and "hotel B" under the same entity type "hotel". And it won't work when I import an updated version.
Now I group them into a single entity "hotel" and then it works for me.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |