Forum Discussion
Hi,
many thanks for the history idea! I didn´t know that there is a FormView or even FormPrint option! I had a similar question in the past where these functions would have been useful!
https://community.aras.com/discussions/development/what-is-the-best-way-to-secretly-observe-my-users-to-see-if-they-use-specific-it/8510
An alternative idea to address the use case in this thread:
In our company, we use a "trophy" column in the part list that indicates how often a part is used. It was initially introduced to help eliminate duplicates. Today, it´s mainly used to help users find commonly used parts. After all, why use something exotic when you can use what everybody else uses?
For the use case above, OnShowItem could trigger a Method or SQL procedure (would avoid an history entry!) that updates the counter. Simply solution that can be removed easily once it´s not needed anymore. But it requires some coding.
- mconstantin_aras_com1 month agoCreator II
Hi Angela
I like this Trophy concept. this can be useful in particular when your Item is a Requirement, a Document or a file. I'll keep this in mind.
for the Part itself, I think a kind of counter based on BOM and Quantity may be more relevant. This can help to suggest user to select the most used Part.
I can imagine an attribute with value list "proposed", "recommended", "mandatory" and that user may have to record a justification when not using the recommended or even needing an authorization for deviation when not using the Mandatory. - carstenw19 days agoCreator II
Hi Angela,
I really like your Trophy concept! Are you able to share the method you use for updating the counter?
- angela19 days agoCatalyst II
I have an idea: I will share the complete throphy project if Aras makes the XSLT processor patch available to the community.😎
Any support from the community is greatly appreciated!
Aras 11SP9 Chrome remove XSLTProcessor | ArasThe BOM Counter Trophy may look simple, but it´s much more than counting added or removed BOM positions. Item copies, deletions, and versioning make it surprisingly complex.
I enjoy contributing to the Aras community and sharing solutions. However, it would be frustrating to share this project while I (and other active open community members) do not have access to essential patches.
I´d rather spend my time building and sharing solutions than creating workarounds for issues that already have a fix. Making essential patches available to the community would benefit everyone and keep contributors highly motivated.