Release 36 Bug Fix: Search Grids Remain Blank and Strange Horizontal Scroll Behaviour
Hello Innovators, In Release 36 we were facing some strange behaviour: Some grids remaining blank even though items where returned from the search query Horizontal scrolling on grids would result in columns being mixed and glitching After some debugging, we found the issue was caused by 3 files. Attached you find those fixed files and a readme.txt on how to implement them. [View:/community/cfs-file/__key/communityserver-discussions-components-files/10/R36-Blank-Search-Grid-_2B00_-Horziontal-Scroll-Bug-Fix.zip:320:240] I hope this can help anyone else facing this issue. All the best, Daan
CUI Table views not working
We have found a strange issue with the tool. We have found nothing in the available installation guides and support forums, and we would be very grateful if you could help us figure out the underlying issue here. We have an installation of Aras Innovator 2024 (2024 Release Build 14.0.25.40942) that was working for a while, but last week, it started to throw error messages whenever we open any table view (e.g. the Requirement table), or we use any user interface feature related to this view, e.g., change pagination size, select a requirement, etc. In each case, the error message relates to the favoriteLayoutData settings being not found. More specifically, the following message was emitted: > The method 'cui_common_layouts_init' failed. favoriteLayoutData.settings is undefined Client Side Error We have tried to reset the user preferences and try it out with another user, different browsers, and cleaning up locally stored cookies, but the issue persisted. We have also checked the server logs but have not found anything that might be helpful. The issue breaks the user interface quite severely, making it basically unusable, but have no idea where to look for possible causes.
Revisions/Item Versions appearing blank
Hi all, Created a new ItemType. Initially, when viewing an instance, Views > Revisions displays the Item Versions. However, after creating a few items, it then appears blank, as illustrated here: I haven't changed anything (as far as I know), it just stops rendering after some time. Any input would be greatly appreciated. Aras Version 11 SP9. Thanks very much.
Bug Report - CAD Document Comparison Rotation
Hi there, I've encountered a bug in Aras version 23. This was previously reported by my organization in version 12SP9 and was confirmed fixed, but appears to have been re-introduced. In brief: Create a CAD Document - ensuring versioning is enabled Add a viewable PDF - save Edit the CAD Document - change the viewable PDF - save Go into the PDF view and user the comparison function Both images get rotated 90 degrees clockwise and the bottom of the PDF gets chopped off. Has this been re-addressed in a later version of Aras? Thank you, Phil MacIntyre SSI
Authority Mismatch on Settings vs. signin state after upgrading from R21 to R27
My R21 environment (dev) had no issues prior to applying the R27 patch. Can't get his resolved. Hopefully somebody else in thee community have had this and resolved this issue. From oidc-clinet-ts.min.js: this._settings.authority !== t.authority && r.throw(new Error("authority mismatch on settings vs. signin state"))
TypeError: Cannot read properties of undefined (reading 'itemTypeGridPlugin')
Dear team, We are currently using Aras version Release19. However, when attempting to perform searches for both parts and documents, we encounter an error stating "TypeError: Cannot read properties of undefined (reading 'itemTypeGridPlugin')." This error is causing the search operation to fail. Could you please advise on how to resolve this issue? I have already checked the error log, but I couldn't find any relevant information. Attaching screenshot for your reference. Regards, S. Senthurpari
Decimal and Float precision, rounding and overflow errors
I am looking for a solution to the following problems that I am encountering using 12.0 SP9 with Float and Decimal data types. I need to store engineering data that can contain very large and very small numbers. In testing a property using the Float and Decimal types I find that both have problems storing the full precision that SQL Server supports. For Float, large numbers work as expected from -1.79E+308 to +1.79E+308. However small numbers do not. The smallest number that I can store in a Float property from the Aras item's form is 1E-20. I can not store any more digits of precision (for example, 1.000000000000001E-20), either entering the value in scientific or decimal notation. Using MS SQL Server Management Studio I can manually edit the item to store smaller numbers in the database (down to the minimum of 2.23E-308). However these are rounded to 0 in Aras. As an aside, despite the documentation and training saying that you need to specify Precision and Scale for floats, neither of these appear to have any effect on how the Float column is specified in SQL Server - it always uses the default 8 byte float size. For Decimal there are problems with precision, rounding and large numbers. Here Precision and Scale really do matter, as they should. For Precision of 38 and Scale of 0, I should be able to store values up to 10^38-1 = 99999999999999999999999999999999999999, and I can do this directly in SQL. However Aras gives a Conversion Overflow error in search grids and the item form if this is stored in the database. The largest number that Aras can handle is 79228162514264330000000000000. This happens to be 2^96 rounded to 16 digits of precision. If Scale > 0 is specified the largest number possible is reduced. Aras only seems to be able to store 16 or sometimes 17 precise digits in the Decimal type with Precision set to 38, and the rounding behavior is inconsistent. For example entering 11111111111111111 rounds up (!) to 11111111111111112 when the item is saved. 1111111111111111111 also rounds up to 1111111111111111200, but 1111111111111111100 rounds down to 1111111111111111000. My best guess is that Aras is performing internal conversions that result in the rounding and overflow problems, since using SQL Server directly works as expected. Is this a known bug? Is there any way to work around this behavior? Do later service packs fix these issues? Thanks
Warning: Versioning and tab pane very buggy in new Innovator versions!!! Are you affected?
Hi community, I need your help to investigate an error that occurs in newer Innovator versions. In my case it occurred in Innovator 12SP17 and 12SP18 but NOT in Innovator 12SP7 / 9 / 10. I look for a bug fix for this one, cause unfortunately Aras rate this one as unimportant glitch and not as high risk behavior. From my POV the bug is a huge source for trouble (data loss!!), so I just can warn people to update to SP17 and SP18 without this bug fixed. I want to investigate, which service pack version is NOT affected by this bug. I am not able to test out all available service pack, so I would be happy if community could help: If you are a user of Innovator 12 SP11 / 12 / 14 / 15 / 16 / 17 I would be happy if you could test out at least the Error 1 scenario!! (2 minutes required!) Scope In 12SP17 and 12SP18 the tab pane can crash to easily when using item versions (like in Parts, Documents and Methods). In addition, old item revision can overwrite the latest item without the user noticing it! Both errors can occur easily, as soon users display previous revisions of an item. Comparing old and new revisions is a typical work during a Change Management process, so it´s an error that affects daily work of PLM users. Test Setup If possible perform this test in a test database. No data is edited during the test when you closely follow the instructions. But I don´t want to bring you in trouble in case of error! 1. Go to TOC -> Administration -> Open ItemType "Method" search grid 2. Search for Method with with "Ver 2" or higher, to ensure the Method has more than one revision. (If you need extra safety, create a temporary custom Method for this test that you can delete after test finished) 3. Open this Method (it doesn´t matter which one) 4. Open the 'Versions' dialog 5. Select a previous version (e.g Ver 1) of this Method 6. A Form with the previous version of your Method shall open. 7. Do not touch the new window with the previous version 8. Simply switch back to the tab with the newest version of the Method and close the "Versions" dialog We now have both versions in parallel in the tab pane. This is our basic setup. So far everything is fine. Reproduce Error 1 (Tab pane crash) 1. Start from setup above. We are in the tab with the latest revision 2. Click "Edit" (but do nothing else)! 3. Now just switch back to the tab with the previous revision of the Method and simply close this window 4. After closing the previous revision, we will automatically jump back to our latest revision tab 5. Click "Discard" as we never wanted to edit anything 6. Now the error should happen: In case of error a second tab reappears. We now have the two tabs for the item. They do not work and you cannot close them. Tab pane is crashed. Everything will be fine again after restarting Innovator in browser. If you don´t see this error, your Innovator version is not affected by this bug. You can skip all other tests. Please share which version you used! Reproduce Error 2 (glitch) 6. When you directly click "Search Method" in the TOC after above error occurred, a small additional glitch can appear 7. As our tab pane is crashed, the search grid will overlab with the Method Form. None of the tabs can be used reliable anymore Reproduce Error 3 (previous revision overwrites latest) Warning: Perform only in test database! Use a custom temporary Method for testing out this one, cause it can corrupt your data!!! 1. Start from setup above. We are in the tab with the latest revision. 2. First switch back to the tab with the previous revision. This time do not close the window, but simply take a look at the "Edit" button. It´s grayed out and you cannot use it. (This is correct behavior, as we never should be able to edit previous revisions) 3. Switch back to the latest revision and click "Edit" 4. Again switch back to the previous revision and take a look at the "Edit" button again. This time it´s not greyed out anymore!!! 5. It´s now theoretically possible to click the edit button inside the Form of the previous revision! 6. In case you click the 'Edit' button, you can create a high risk scenario: 7. After clicking the 'Edit' button, it´s seems to be possible to edit the previous revision. But what you see doesn´t represent the "truth" any more. a) The shown Method code still shows the content of the previous revision b) But the context item has switched to the latest revision. But this revision change is not visible to users as they still watch the previous code/properties. You can only see it in the 'Generation' value in the 'Properties' dialog. If you now save your "fake" previous item, the latest item will be overwritten with code and properties of the previous version. This is a high danger situation not only for Methods, but for all ItemTypes that use revision as it will lead to data loss and corrupted data. Conclusion I discovered the bug while merging a few upgrade patches and actually destroyed a few Methods cause of this bug. If I as admin fail to handle versioned items cause of this behavior, I expect that real users will face the same problem soon. I right would not recommend to use 12SP17/18 just because of this bug. Comparing and working with item versions is a daily task especially when using Change Management. But it´s important that users can trust the data they see. Right now working with revision in SP18 is very risky cause users can crash their tab (best case) or overwrite data without knowing (worst case). Please let me know if you are able to reproduce any of the above bugs in your Aras Innovator version! If you´re Innovator version doesn´t show the bugs, please also write a short post! When we can determine in which service pack the error appeared first, it´s maybe possible detect the bug more easily. Thanks for your help! AngelaGUID showing up in keyed name on change of an item while in edit mode.
After creating an item, if I open the item back up and make a change to it, the keyed name changes from its original name to the GUID. In this case the original keyed name was 'Concept-0047 1' but after making a change it switched to the guid of the item. If I save the item it will go back to the original name of 'Concept-0047 1' so it is only an issue if the user is editing the item. If there is a solution to this please let me know.HTTP Error 502.5 - Process Failure - OAuth - Server
Hello, After installing ARAS Innovator 12 SP9 community edition, I got the HTTP Error 502.5 as I tried to login onto the new instance. First thing I did was checking the prerequisites for ARAS innovator, but everything was ok. So I started to analyse the underlying problem, and it turned out that the XML file .../OAuthServer/OAuth.config is not a valid XML document. At line 86, you find "1:" right before the "redirectUri" tag. Please remove this two characters and it will start to work. Hope this is helpful until this mistake is fixed. Best regards
