AgExpert Analyst allowed users to edit the agristability codes and names, as well as delete codes no longer in use. This would help keep the list clean and concise. As well, I have spoken to some customers who said after they migrated their data the names of the assigned codes were different, and this caused them to make some adjustment mistakes.
This is exactly what I was going to request - I use these codes for 'buckets' for each crop year (ie. 2026 Durum) and then I am able to pull crop from the year it was harvested as it is sold. However, the list is so long it is cumbersome and inefficient
Thanks Diane! I am digging into this one.
Choosing Agristability codes is terrible in this program, had I known that payroll updates would still be sent for Agexpert I never would have changed. There is no way that there should be 2 #2 canola in the codes as there wasn't before migration and there is no way to get rid of one. We shouldn't have to scroll trough dozens of commodities if we are only growing 4 or 5
definitely need this