Status Update
No update yet.
Comments
ds...@google.com
ds...@google.com
Hello,
To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue:
- Has this scenario ever worked as expected in the past?
- Do you see this issue constantly or intermittently ?
- If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
- To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
- It would be greatly helpful if you could attach screenshots of the output related to this issue.
Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.
Thank you for your understanding and cooperation.
ds...@google.com
Thank you for reaching out. Here is the information requested regarding the reported issue:
In response to the first point, I previously conducted an uptraining with approximately twenty bank statements, and this issue did not occur.
For the second point, I have attempted the uptraining three times, and the same error appeared each time.
To reproduce the issue: I labeled 76 bank statements, dividing them as follows—59 in the training dataset and 17 in the test dataset. I also modified the label schema by deactivating the following labels: account_types, bank_address, bank_name, client_address, and client_name. Additionally, I created a new label for rib (bank account identifier). I then proceeded to uptrain a new version, and the issue arises during this process.
I hope this information helps clarify the situation. Please let me know if you need any further details.
Thank you for your assistance in resolving this matter.
ma...@axpo.pl
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
If you are looking for a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
I recently used Document AI: Custom Document Extractor and used names containing the "-" sign to create labels. However, after some time I noticed that the possibility to use this character in names was blocked. The real problem appeared when I exported documents from one processor to another. Those labels that have a minus sign in the name cannot be edited in any way - when you click the "save" button, nothing happens (other labels can be edited without problem). I have several hundred documents with such names and re-labeling would be very hard.
What you expected to happen:
Get a possibility to edit labels containing "-" sign in names.
Steps to reproduce:
I can't share documents because they contain personal information.
1. Export dataset from Custom Document Extractor processor with schema containing labels with "-" sign.
2. Import in other Custom Document Extractor processor.
3. Edit labels containing minus sign (Here the problem shows).
Other information (workarounds you have tried, documentation consulted, etc):
Screenshot explaining where the problem is.