When you have completed an application and are ready to push the PUR to Agrian, there may be some issues that come up. Below, we talk about these and what to check to make sure everything will go through properly.
To reference information on how to setup Agrian and AgVerdict please read this first: Agrian and AgVerdict Information Sync
Site ID issues
When pushing a PUR to Agrian, if the information between Agrian and AgVerdict aren’t setup correctly it will cause an error. The Site ID in AgVerdict needs to match the Site ID in Agrian.
- Check the site ID in Agrian. If there is no site setup, create one.
- If there is a site ID, go into Bulk Update in AgVerdict and check that the field has the matching Site ID. If the Site ID does not match, update it to match Agrian.
Start and End Date
When pushing a PUR the START time needs to be before the END time. If they match, you will receive an error.
- To fix, edit the application details for that land and ensure the End time is after th Start.
- Then Save and resubmit the PUR to Agrian.
Acreage issues
There are a couple issues that can be seen when regarding the land area.
- Acreage is not matching what Agrian has for that Site.
- If this is the case, change the acreage in AgVerdict to match Agrian. Then re-submit.
- Too many decimal places.
- Agrian will only accept up to 2 decimal places. If AgVerdict has more than 2 places, edit the amount to 2 places and then re-submit.
Products
( Fertilizers and PPP)
There may be some instances where the product that is on the PUR has issues. In most cases this has to do with the products that are currently saved in Agrian.
- To address this, go into Agrian and into the products list. Remove the product that is causing the issue. Go back into AgVerdict and re-submit.
Wind Speed
In some instances the wind speed entered could be too high.
- If this is the case, edit this information in the App event details and re-submit the PUR to Agrian.
Split Location
Currently there is sometimes an issue when you have a location that has been split that will cause problems when being pushed to Agrian. To address this:
- The issue usually is around the two locations having decimal places.
- Remove the decimal places from each location so they are whole numbers and then re-submit.