You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello, I currently have an Object Schema that I am using to store Customer Organizations and Employees. I would like to extend this to include our product versions. Currently, I have a custom field that uses a picklist (IE: 1.0, 1.1, 2.0, 3.0) that I manually update upon new releases or when a version is retired. When a version loses official support, I create a new option (ie. "1.0 (unsupported)") and disable the version so it can't be picked. This informs customers when opening a new ticket that the version isn't officially supported.
I'd like to switch to using Assets and develop the schema in such a way that I can accomplish the following.
My questions are three-fold:
I think I understand how to restrict the field options based on AQL queries, so the structure and automations are my main hurdles right now.