This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 76%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Can copy API be used for copying composed model from one Form Recognizer resource to another.
I have POSTed a copy request which was accepted with HTTP 202 ; but copyresults API is still showing "running" after 10 hours. Trying to understand what would be the issue here
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 45%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi, yes Copy API can be used for composed model copy as well. Can you share the current status?
It was in status "running" after 24 hours as well. Azure seemed to have an issue with new form recognizer resources and subscriptions the day when i tried it.. My resource was not showing in portal as well. So after 24 hours, i deleted the model and resubmitted a copy request which worked fine.
I was using copy for migrating models to stage/prod form recognizer from my dev form recognizer resource.
Composed model copy worked good. But in analysisResults "docType" was not showing the model name of actual model. it was showing only the composed model name like "custom:<composedmodelname>". Generally it comes as <ComposedModelName>:<ActualModelName>.. we have different logics in our code to process response for each model for which we are relying in "docType".. So I end up copying all individual models and compose again in the target resource. It would be helpful if this issue can be fixed or an alternate option is suggested. Thanks for your help
Are you saying you expect it to show as <ComposedModelName>:<ActualModelName> instead of custom:<composedmodelname>?
Yes , for my composed models, I am getting it like below
"docType": "ComposedModelName:ActualIdentifiedModelName",
For non composed models it comes as custom:ActualIdentifiedModelName.
Since our processing logic is different, we have coded system to route to different processing logic based on ActualIdentifiedModelName retrieved from docType.. If we code with modelId, every time model is retrained, we would have to update our code/table. Hence using docType for that logic..
Can we not expect it this way.
Okay, will forward your feedback to the product group and share updates as soon as possible.
Thanks a lot. It would be very helpful if we can get an opinion from product team soon. If they do not expect us to code processing logics based on docType; I can change to do it based on model ids which I am hoping would be always accurate.