I suggest you...

Allocate serialized components without allocating serialized container

It would be great if you could control individual assets even if they are attached to a container.

For example;
I have 5 microphones in a box where the box is the container. When I allocate the box the Mics also allocated. Which is great.

However, this means if, on a different job, I only want two of those microphones, I cannot individually allocate them as they are attached to a parent container.

It would be great if items can be individually added to a job, even when they are in a container and the rest of the items are only allocated when the parent container is scanned.

Almost like an optional container? Where it's only a container when the parent container is scanned.

10 votes
vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Kieran shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Darren Doyle commented  ·   ·  Flag as inappropriate

        Have a container of serialized items that you do not have to scan all the items just the container. Also, be able to rent the individual items if needed without resetting up anything.

      Feedback and Knowledge Base