---

---

I took a preliminary look at Metrc Bulletin 101 and I think that it should be an easy one since we already have the functionality in other states. I will have to dig in a little on Monday to see if there are any missing pieces or if we have to add in the state initials into some if statements. 

DS Notes:

This Task took 3 hours and 16 minutes.

1: I searched the entire stack for instances of /labtests/V1/labestdocuments and /labtests/V1/record and found that the only instances where in cfm files related to taking the metrc state accreditation tests and so determined that the updates to these PUTs and GETs would not affect us.

2: I searched the entire stack for instances of GET /locations/v1/types, POST /locations/v1/create, POST /locations/v1/update and again found that the only instances where in cfm files related to taking the metrc state accreditation tests and so determined that the updates to these POSTs and GETs would not affect us.

3. I searched the entire stack for instances of POST /harvests/v1/create/packages, POST /packages/v1/create, POST /packages/v1/create/testing, POST /plantbatches/v1/createpackages, POST /plants/v1/create/plantbatch/packages and found that there are many of each of these POSTs. I then first looked that for each instance of these endpoints included Nevada, and in each case were they did, I looked to make sure that the Location endpoint was being updated properly by ensuring a connection between a user selected/entered location and the location endpoint as needed for each specific POST.