Found another ancient thread with my current problem!
Is there any solution to this? I just loaded 3282 xProperties into my xClassificationTree, and now my parts search is totally hosed...
Do we know the limits of Extended Classification? How many xProperties can it actually handle? Does it matter if those properties are lists? Does having more xClassificationTrees help if they are tied to the same ItemType?
I tried to delete a part in the interface and I got the message, before the search crashed. Tried it through REST and I think its the same message:
"error": {
"code": "SOAP-ENV:Server",
"message": "The number of elements in the select list exceeds the maximum allowed number of 4096 elements."
}
Guess I'll probably have to gut my xClassificationTree and try something else, if OP is correct, each xp field generates 3 selects, putting the max at 1365 or so...
