Forum Discussion

Duke's avatar
Duke
Ideator III
8 years ago

Extended Classification XP Property has Limitation

Hello, I current use the version of Innovator11SP12. I also has big Xclass tree for Part and has total over 2000 xp-propertys. When i maintain Part record,the SQL server always throw error message for me. The error message is “The number of elements in the select list exceeds the maximum allowed number of 4096 elements.” So i using SQL server profiler watch execute SQL command! My jaw dropped . OMG, Make me Amazing! The Aras InnovatorCore will dynamic generate huge select fields in sql command. Maximum Capacity Specifications for SQL Server limit for Columns per SELECT statement: 4096. URL: docs.microsoft.com/.../maximum-capacity-specifications-for-sql-server Just like this exec sp_executesql N’SELECT [PART].[APPLY_REASON] AS [APPLY_REASON], [PART].[BOM_PLANT] AS [BOM_PLANT], ……. PART_XPROPERTYVALUES22.[XP-PART_0101_CORE_SHAPE$IS_DEFINED] [XP-PART_0101_CORE_SHAPE$IS_DEFINED], PART_XPROPERTYVALUES22.[XP-PART_0101_CORE_SHAPE_$_PERMISSION] [XP-PART_0101_CORE_SHAPE_$_PERMISSION], [PART_XPROPERTYVALUES22].[XP-PART_0101_CORE_SHAPE] AS [XP-PART_0101_CORE_SHAPE], — so huge xp property select fields , one xp property field will generate three select field ON ([PART].team_id = fk12.id) LEFT JOIN [secured].[XPROPERTYVALUES22] …. Then, it will generate total select fields over 4096 fields. Touch SQL Server limitation for max select fields. Even i split one xclass tree to a lot of small tree not solve the problem. How do i solve the problem?

3 Replies

  • Hello, Could you also let us know how many regular properties are on the Part ItemType itself? Chris
    Christopher Gillis Aras Labs Software Engineer
  • Duke's avatar
    Duke
    Ideator III
    Hellos,   Just 200  regular properties are on the Part ItemType !
  • 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...