This is a feature that needs to be turned on in Toolbox Settings tab > Object / Class: Allocate Object Even If Its Not Available.
The following setting needs to be ticked off: Auto Book External Object When No Object Found.
If you choose this option " Allocate Object Even If It Is Not Available" and book an Object Class like "camera" and allocate one member at a time when all Members of that Object Class are already booked, farmerswife will always take one and the same member of the Object Class and create a Conflict.
This setting was developed for those clients who have the sell prices on their Objects and use Bookings to create their quotes. They need to know if they have the equipment available so they need to double or even triple book the equipment and it always nees to hold the correct price. However when there was a "No Object" Object due to no available Objects there was no price in the quote.
Behavior 1:
Object Class Car is fully booked on one day (meaning all members of the Car Object Class (Big Car and Small Car) are booked).
If you do a new Booking now taking the Object Class Car and dragging it to the same day and allocate 1 Object, always the same Object (for example "Big Car" will be booked and be in conflict. See the picture. In this case always the Big Car gets into conflict. Never the Small Car. Big Car is the Object that is first in the list of the Object Class if you open the Object Class in the Object Manager and have a look at the members:
Behavior 2:
If you create a Booking via the Object Class Car on the day where all members of the Car Object Class are booked and you allocate one more Quantity than Members that you have (Object Class Cars = 2 Members, now you book Quantity: 3) in that Booking farmerswife will allocate one NO OBJECT Object.
Behavior 3:
At Object Class level, in the Object Class modify window there is an option to "Randomly Pick Object".
Example: Object Class "Baseplate" with 4 Baseplates in it. Setting: Randomly Pick Object is set on the Baseplate Object Class. All 4 Baseplates are booked for the day.
Now create a new Booking by dragging the Object Class Baseplate onto today. The conflict that will appear, won't be on the same Object, but will appear on different Objects. The pattern it takes is that it will create a conflict on the first three items inside of the Object Class and then start from the top again:
See here:
--> Baseplate 803004 gets booked in Conflict
Book one more Object via the Object Class
--> Baseplate 803003 gets booked in Conflict
Book one more Object via the Object Class
--> Baseplate 803002 gets booked in Conflict
Book one more Object via the Object Class
--> Baseplate 803004 gets double booked in Conflict. Now it has three Bookings, one confirmed and two in Conflict.
Book one more Object via the Object Class
--> Baseplate 803003 gets double booked in Conflict. Now it has three Bookings, one confirmed and two in Conflict.
etc. 