Log how many times an item has been opened
Hello, we are looking into measuring how much items/modules are beeing used by our users. I think if you add a client method to a item, that should be no problem with an OnShowItem event and then increase a number on a table somewhere. But is there are global approach that we don't have to insert such a method in each item we want to track? Any ideas are welcome, thanks in advance.
Report Manager shows blank page on Aras Innovator 14.35 CE – Hotfix and Reporting 29 guidance needed
Hello Community, I am evaluating Aras Innovator 14.35 Community Edition and am currently facing an issue with Report Manager, where the result page is displayed as a blank screen. Before asking, I would like to clarify that I believe I understand the separation of concerns, and I am seeking confirmation on the correct and minimal path forward. Environment Aras Innovator: 14.35 Community Edition Build: 14.35.0.44037 MS Build Number: 000000.00 Browser: Chrome / Edge (same behavior) OS: Windows Server (IIS) Observed issue When executing a report (Type: General) from Report Manager, the result page is blank. From the browser network trace, I can see that blank.html is requested with an incorrect URL where an X-salt token is injected into the path, for example: .../InnovatorServer/Client/X-salt=std_14.35.0.44037-X/scripts/blank.html Instead of: .../InnovatorServer/Client/scripts/blank.html The AML itself executes successfully (InnovatorServer.aspx returns 200), so the issue seems to be on the client / UI side. What I understand so far Please correct me if anything below is wrong. 1. Hotfix / Patch Hotfixes apply to the Innovator core (Server / Client). MS Build Number = 000000.00 indicates that this environment is likely running a base build without Hotfixes applied. Therefore, this blank page issue may already be a known issue fixed by a Hotfix. 2. Reporting Aras Reporting is a separate product and installer. Reporting 29 requires a dedicated license (Aras.Reporting) and installation. Reporting 28 is not required if installing Reporting 29 as a new installation. My questions To proceed efficiently without rebuilding the environment, I would appreciate guidance on the following: 1. Is it correct that applying the appropriate Hotfix for Innovator 14.35 is a prerequisite, and that Reporting alone would not resolve the blank page issue? 2. Is the blank page / X-salt URL issue a known problem in the base 14.35 build that is addressed by a specific Hotfix? 3. For a Community Edition evaluation environment, is it realistic to: obtain the required Hotfix, and obtain the Aras Reporting 29 CD Image as part of the same guidance / recommendation? 4. If Reporting 29 is installed after the Hotfix, should Report Manager work as expected without additional undocumented steps? Goal / Constraints The goal is to evaluate Report Manager functionality. I would like to avoid rebuilding the existing test environment if possible. I am looking for the shortest correct path, even if it involves multiple steps, as long as the sequence is clear. Any advice, confirmation, or references would be greatly appreciated. Thank you in advance.
UI doesn't load for one user - anyone had a similar problem?
On our test server, on one particular database, one particular user doesn't get an UI when logging in. I've tried digging into the frontend calls, and it seems it's this call: https://{our test server}/Server/MetaData.asmx/GetConfigurableUi?accept=json&database={one particular db}&date=2025-05-02T13%3A01%3A58.94&item_classification=%25all_grouped_by_classification%25&item_type_id=&lang=en&location_name=TOC&user={me} which fails, with a "not a single item" fault. I am in fact logged in, and can e.g. go see the session information on the user button. Deleting all client side caches or logging in with incognito mode makes no difference. Have anyone else experienced this?TreeGridView performance
We have "changes" tab to list, in a tree grid view, the change objects which have gone through on a given Part. However, loading this tab is terribly slow. I have found out that the query itself is quite fast. When I run it in the query editor, it takes less than a second. However, the Tree Grid View can take almost 20 seconds to load. Even on a fresh part with no change items, it takes 15+ seconds. The call which takes time is an odata call to /Server/odata/method.rb_GetTreeGridData, which takes the entire 2500+ line rb_TreeGridViewDefinition as input (why? It's a server side method, although a very odd one I can't see the implementation of, and the data it gets passed lives on the server too!) Have anyone had any success in optimizing the loading of tree grid view structures?
Item.apply overwriting action, has it always done this?
After upgrading from version 12 to 31, we started getting an error when saving a certain custom datastructure, developed for us by Minerva back in the day: Failed to execute 'serializeToString' on 'XMLSerializer': parameter 1 is not of type 'Node'. From what I can tell, this happens because Minerva's old code calls an action directly on the document.thisItem object var output = document.thisItem.apply("VE_GetCopyTreeGridHeader"); which "pollutes" document.thisItem with that action. When later hitting save, it calls this function instead of doing whatever it ordinarily would (probably a get action), resulting in the error. I observe that if I change the action to "get", it gets rid of the error message and saves any changes in the object itself, but not in a related items treegrid associated with it. If I change the Iaction to "update", it saves everything correctly the way it used to do in version 12. I see that the docs on item apply says that it overwrites the action, but if it always did that, how did this code ever work? (By the way, that .apply() overwrites the action is an error-prone side effect which I can't see any good reason for)Making changes to typescript files in the tree
I tried to apply a trick from a previous post: How to open StartItem directly without the helper window - Development - Aras Community - Aras Community However, that file is now a typescript file in my tree. I guess that means I need to transpile it to javascript/do whatever else you at Aras do in your frontend build process, in order for it to end up in the right place? What is the recommended way to do this?
