"Key detection failed" (1 reply)
Randy, we believe we're resolved this issue in Product Update 1 for version 3.2.
Randy, we believe we're resolved this issue in Product Update 1 for version 3.2.
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
Realisable Software Ltd provides code-free, cost-effective applications integration solutions for SMEs. Our core IMan product is designed to integrate almost any application with a number of Sage solutions and online payment processors.
Looking to purchase IMan, please see our resellers here.
Realisable Software
Ph: +44 (0) 208 123 1017
Copyright © Realisable. All rights reserved.
Realisable is a registered trademark
I'm trying to use the Excel Reader on a 1997-2003 Excel file (.XLS), but I'm receiving the error "Key detection failed due to nesting level in file too deep or key field is too long. Revise settings and refresh."
Can you provide any additional information on this error, such as how to resolve, or what to look for?
This was a ~30 column Excel file with pretty basic (and not excessively long) column names, so I'm not sure if IMan is having an issue with the column names.
There are *some* fields which have a good amount of HTML content, which I thought might be the "nesting level in file too deep", but even after removing most of that HTML content, it appears that IMan is still running into the issue.