I use IXP in my Document Understanding process.
I done build in IXP: so i created taxonomy, annotate and validate predictions, and publish the current version as stagging.
In my studio, i build the similar taxonomy as the one in IXP.
I use Document Understanding Project Extractor to connect them together.
IXP taxonomy has 2 field group.
Field group 1: Employee’s Basic Information
Field:
The error usually stems from a document type ID/version mismatch rather than from the grouping itself. Please verify that Studio is using the exact same DocumentTypeId as the IXP project, and that the Project Extractor is connected to the same published Staging tag/version. Also, refresh Get Capabilities after republishing.
Your setup looks mostly correct. The issue is likely due to a capability mismatch rather than field grouping or credentials.
In IXP, tags are not just for filtering—they determine which project version (and its taxonomy/document types) is used at runtime. If the tag (e.g., Live) was updated or you recently published Version 17, Studio may still be using cached/older capabilities, which leads to the “No suitable document type found” error.
Recommended steps:
Use Tag = Live instead of Version (since Version 17 is already Live)
Refresh the project and run Get Capabilities again
Ensure the taxonomy in Studio is synced from IXP (not manually recreated, to avoid document type ID mismatch)
This usually resolves the mismatch between Studio and IXP schema.
i indeed build taxonomy in studio manually. can you advise on how to sync it from IXP? is there any method to do so?
and another question.. if you look at my explanation earlier, i mentioned that IXP taxonomy has 2 field groups. In Studio taxonomy, i represented them as tables with the IXP fields as columns. Is this correct?
Correcting my earlier miscommunication: there isn’t a direct “sync” of taxonomy from IXP to Studio. In Studio, taxonomy is created manually and then aligned with IXP using Get Capabilities and the mapping wizard, which is correct.
Your approach is correct: mapping IXP field groups → Studio tables and fields → columns.
Action Items:
The error you’re seeing is most likely due to a capability mismatch after publishing Version 17/updating the tag. Studio may still be using an older schema.
Regarding Version vs Tag: you’re right—they can’t be used together. Since Version 17 is already marked as Live, it’s better to use Tag = Live (this always points to the active version at runtime).
Hope this helps resolve the issue. If you’re still facing issues, try resyncing the wizard and updating the tag.
Hi Karthik,
Unfortunately changing tag is not working for me.
I’m wondering if my Studio taxonomy and IXP taxonomy has a gap somewhere that causing this error. Can you help me to check and find the missing hole in taxonomy if any?
I attach the taxonomy files here. Please be informed that in my Studio i have another document called FORMIR8E. You can ignore it cause it has no correlation with current issue. IXP Taxonomy.json (13.6 KB) Studio Taxonomy.json (23.7 KB)
I compared the IXP and Studio taxonomy JSONs for SG Pay History. I do not see any missing taxonomy gap: the two IXP field groups map 1:1 to the two Studio tables, and all child fields match. The issue is more likely a capability refresh/runtime configuration problem rather than a schema problem. Please refresh Get Capabilities and Configure Extractors, save the mapping again, and confirm that the workflow is routing the document to the Studio document type ID default instead of the unrelated FORMIR8E type.
I assume you are running a Studio project connected to the same tenant as the project in IXP. Please run step by step in debug mode to see if it’s getting classified correctly.
