+2We need to be able to associate an already discovered asset to a Purchase Order. Your customers need this in order to bring in historic information or fix data that is entered wrong. The solution was developed for a VERY specific workflow, but lacks the flexibility for real world operations.
NOTE: The suggestion to “delete the existing asset and add it again through the PO” is not a reasonable solution.
+2Oh, and you can’t effectively delete an asset at all which makes the suggested work around completely ineffective. The article below eludes to the issue that I am now having. I deleted the computer that was added by the agent so I could add it via the PO, but I can’t b/c the asset is still in the database somewhere. I can’t see the trash that they elude to in this article. It’s a mess...
This is going to happen a LOT for assets that existed before we switched to Freshservice and before we were creating POs (because we weren’t using that feature before). We have about 400 assets, all of which should be linked to a hypothetical POs, but the PO feature is essentially useless to us if we cannot link all those existing assets to POs.
+1This makes sense from a normal usage perspective as well, not just an import perspective.
If a device goes out for repair, it would be nice to be able to keep a historical record of that via a PO instead of the very generic “Expenses” functionality. (And even get approvals for high-ticket items.)
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
