So 1+1 = 2. Not all the time!

An SA called the other day with what appeared to be an issue with the application updating the Unit Count of an existing Asset. She and I both studied the issue for a moment and in the end, not wanting to hose your Inventory I elected to speak with those smarter than me in the wiley ways of databases.

Here… let’s see how you do with the problem.

You have an Asset with an original Unit Count of twenty-five Units. Last year six of those Units were retired due to wear and tear. You were a good SA and flagged the six specific instances “retired” as Unavailable on the Asset’s Case#/ID screen, the Unit count was now correct at nineteen for customer selection and the history for the original six Units was preserved.

Now your customer buys two new identical Asset Units and you want to increase your Unit count for the existing Asset accordingly. So you go to the Edit an Asset screen and increase the displayed Unit count from nineteen to twenty-one, right? WRONG!

While the Available Unit count is nineteen the db knows better. There are already twenty-five Asset Unit Records in the system. Moving the value in the Unit count field from nineteen to twenty-one made no sense at all to the db as it was perfectly comfortable with the fact that there were already twenty-five Unit Records.

So what do you do? Maybe this update to our Edit an Asset screen will help.

If you are still still stuck give me a call.

The update also gave me a chance to have the text above display only for Assets that return to Inventory and have updated text unique to Assets that Do Not Return to Inventory.

A genuine 2 4 1.