fixes some issues with miseq projects

A project I can't name generated an error, and this should fix it
AssertionErrors are quite common in the genologics package.
Every entity created with no ID or URI will cough up an assertionError, and wrong udts will raise assertionErrors.
I assume that the idea behind this is that since you can create any lims entity with either an id or a uri (because if you know the type, both informations are equivalent), then the person who wrote the entity class decided to avoid calling the api with a "None" parameter, which is a good thing as it saves both time and ressources. 

The only other way to handle this would be to test wether steps.latestdem['outart'] is None or not, and I thought that I was to follow the guidelines on "try rather than test". 

I can add a comment explaining what an AssertionError means in the context of the genologics package, but I would have to add that every time we create a lims entity with a parameter that might be "None". 

The other way around is to test the value that's given to id rather than try, would you rather have that ?