Forum Discussion

Former_Member's avatar
Former_Member
Accelerator III
9 years ago

bug Report - Recreating an reserved property

In short... If you delete a pre-defined item property, in this case - item number, and then later recreate it, it will throw a String or Binary truncation error exception when trying to save an instance of that item type to the database. The exception returned only shows the variable names and not the actual data being entered and the form was being filled out with only a single required field, the item number. I've rolled back my DB a couple times dealing with this and its the only thing that comes up. It seems like the exception is getting thrown improperly too or the database is not being properly defined when the column type is readded to the table for the particular item type.  

8 Replies

  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Okay... now this doesn't make any sense. I thought item number was reserved. It was not. Its not automatically generated. It was present in the pre-exsisting base ARAS item types. I attempted to duplicate this again... couldn't do it. Will update it if I figure out how to duplicate it.
  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Okay, Getting that truncation error again. It was during a form modification. Was attempting to add the "major rev" field to the form so it would be exposed to users. Added the element and then disabled the form item. Began throwing Binary or String truncation errors. Killed the form, built a new one. Same error. Not sure whats up, but its repeating so I might be getting closer to recreating. Could anyone chime in on how to track this thing down exactly? I'm rolling my SQL server back to an hour before the error bugged out.
  • christopher_gillis's avatar
    christopher_gillis
    Community Manager
    9 years ago
    Hello, I've been unable to reproduce this issue either with deleting/recreating an item property or with adding a field to a form. Could you please confirm what you mean when you said you "disabled the form item"? Additionally, can you clarify if you are performing these modifications on a standard Innovator ItemType like Part and Document or an ItemType that you created? Chris _____________________________ Christopher Gillis Aras Labs Software Engineer
  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Chris, Now its getting spooky. Got logged on this morning and am no longer receiving the error. To clarify, it was on the standard "model". I I've added a bunch of application specific properties and reversed the product relationship. The Model now has a specified product as a property. I am getting my dev environment setup to debug source code. I should have copies of the DB from when this was occurring. I'll get those copies up and running on my local machine and see if its still reproducing when restored from backup. Tom
  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Chris, Was just working in my "Models" item, plugging along like expected. Went into my Item definition and switched versioning from Automatic to Manul. Now throwing
    String or binary data would be truncated. The statement has been terminated. in SQL: INSERT INTO [MODEL] ( [AM_PART],[ANIMAL],[ANTENNA],[ATTACHMENT],[BATTERY_MAH],[BATTERY_SELECT],[CONFIG_ID],[CONTROLLER_BOARD],[CREATED_BY_ID],[CREATED_DATE],[CREATED_ON],[CRUSH_DEPTH],[CURRENT_STATE],[DANGEROUS_GOODS],[EFFECTIVE_DATE],[ENGINEERING_DRAWING],[GENERATION],[HEIGHT],[ID],[IS_CURRENT],[IS_RELEASED],[KEYED_NAME],[LENGTH],[LOCKED_BY_ID],[MAJOR_REV],[MANAGED_BY_ID],[MODIFIED_BY_ID],[MODIFIED_ON],[NEW_VERSION],[NOT_LOCKABLE],[OWNED_BY_ID],[PDF_3D],[PERMISSION_ID],[PHOTO],[PRODUCT_LINE],[RATED_DEPTH],[RELEASE_DATE],[SALES_DRAWING],[SALES_PRICE],[STATE],[SUPERSEDED_DATE],[TAG_TYPE],[TEAM_ID],[THUMBNAIL],,[WEIGHT],[WIDTH],[MODEL_NUMBER] ) VALUES ( @p0,@p1,@p2,@p3,@p4,@p5,@p6,@p7,@p8,@p9,@p10,@p11,@p12,@p13,@p14,@p15,@p16,@p17,@p18,@p19,@p20,@p21,@p22,@p23,@p24,@p25,@p26,@p27,@p28,@p29,@p30,@p31,@p32,@p33,@p34,@p35,@p36,@p37,@p38,@p39,@p40,@p41,@p42,@p43,@p44,@p45,@p46,@p47 )
    Will try and get into debugging mode to see what I can dig out of this.
  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Can now confirm, failure is coming from a change of revision sequence and is also likely from a copy paste issue. Wanted to run out revisions from 1 to 99. Generated the number sequence in Excel and copy pasted into the sequence input. Looking at the text in the input box, it would appear that it was tab delimitation coming from excel and holding those tabs in the form for revisions. It seems that I was changing back and forth between revision formats and not realizing it when the bug dropped.
  • Former_Member's avatar
    Former_Member
    Accelerator III
    9 years ago
    Little more detail. Any time the format of the "Revision" sequence is not correct, its bugging out. E.g. 1 2 3 4 5 with carriage returns is throwing the error 1 2 3 4 5 6 7 is not throwing the error with spaces. Looks like a good opportunity for some regular expression searches to throw error on any non space or alpha numeric characters.
  • christopher_gillis's avatar
    christopher_gillis
    Community Manager
    9 years ago
    Hi Tom, Thank you for the information. I can confirm that this issue reproduces in my environment as well when using a Revision with a sequence separated by either tabs or a newline. I have filed an issue for this to be fixed in a future release of Aras Innovator. In the meantime, please separate your revision sequences with spaces to avoid this issue. If you expect to be creating additional revisions, it may also be possible to add a server event to the Revision ItemType that will re-format any Revision sequence to be separated by spaces instead of newlines or tabs. Chris _____________________________ Christopher Gillis Aras Labs Software Engineer