You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't yet have this functionality exposed anywhere in the frontend, but our backend supports linking assets to a PuchaseInfo object which records information like date, cost, vendor, invoice number, etc.
When you add an instrument to the application, and especially new instruments, we should prompt the user to optionally supply this information. One way to model this information could be using the Material Stepper component, which would also allow for splitting information up among several pages.
The text was updated successfully, but these errors were encountered:
We don't yet have this functionality exposed anywhere in the frontend, but our backend supports linking assets to a
PuchaseInfo
object which records information like date, cost, vendor, invoice number, etc.When you add an instrument to the application, and especially new instruments, we should prompt the user to optionally supply this information. One way to model this information could be using the Material Stepper component, which would also allow for splitting information up among several pages.
The text was updated successfully, but these errors were encountered: