- There was an original email dated back in July - Cultivation report for Ianthus

- Suzi and Philip from Ianthus were on the call - there were quite a few adilas folks on the call.

- Cultivation mapping - done by Dustin

- When a plat it changed from one phase to other phase, you auto populate those fields.

- They have some custom fields (sub inventory attributes) that they want auto filled when certain actions happen - changes of specific phases

- Maybe setting up which sub inventory attributes show up based on what phase. Also, does one or more of them have (sub attributes) a mapping from other data that is being entered up higher. It may take some more mapping. We may want to show/hide certain sub attributes based on the phases. That means we need to go through the process and really detail out what is shown and what is hidden. Along those same lines, they would love to set it up so that if a sub attribute is being shown, it can get a value or its data from one or more spots (other user entered form values). 

- Currently, some of the info that they are wanting to catch (automatically) is dealing with dates and sub dates.

- As a side note, because we allow each corporation build their own sub attributes, we then have to be able to show/hide and map out these pieces as they go through the different phases. The eventually need all of this data, but we are showing so many fields, it makes it more difficult. We are catching all of the data right now, it just isn't organized (visual report or visual form) to make it easy.

- Another thing that they were talking about was getting to those sub attributes later on - other reports  and passing that data along to other places.

- Just an idea... what if we build a phase builder type app - these would be settings, user controlled, and allow you to setup a single phase, what data to gather (maybe a point and click interface to setup what will show up), then the ability to setup defaults, show/hide fields, what to default things to, other data mappings, etc.

- There were some talks about back filling the data - separate tasks going backwards. Along with that, if we back fill things (update the data), we also need to build it going forward so it becomes an automated process.

- Eventually, they were getting into the nitty gritty details of each phase. The start of one phase sets certain values, the end of a phase closes things down (other actions) and also starts the next phase. We need to detail out each phase. I'm just dreaming here, but virtually a way to setup pods or sections of a virtual data assembly line process.

- The first phase would be a backfill type report - able to do things in bulk. They were talking about being able to select a PO date range and then applying specific dates to all line items on the PO. There were also talks about a PO number range.

- Light talks about required sub attributes and optional sub attributes.