Dutchie (Leaf Logix) Integration
Isolocity is now integrated with Dutchie for the parts, supplier and receiving inspection modules. Dutchie is a GMP (Good Manufacturing Practice) validated seed-to-sale ERP software.
By activating the Dutchie integration, you will be able to import your product inventory, supplier information and receiving inspection data from Dutchie into the Part Manager, Supplier Quality and Receiving Inspection modules in Isolocity.
Setting Up Your Integration with Dutchie:
Generate Your Dutchie Facility Token for Isolocity API Integration
In order to use Isolocity API endpoints, the person responsible for this integration must first be authenticated. For this you will need to request an Isolocity access token.
The token can be generated by your CS Representative.
Retrieve the “consumer_key” and “auth_token” From Dutchie API
In order to use Dutchie API endpoints, the person responsible for this integration must first be authenticated. For this you will need to retrieve a consumer key and auth_token from Dutchie. The token can be generated from the following steps:
Ask the Dutchie Organization admins directly for the respective consumer keys of their company. There will likely be two keys, one for grow and one for processing. Keep both.
Once you receive the consumer key, visit Dutchie swagger endpoints documentation and look for the “util/AuthorizationHeader..” endpoint
http://leaflogix-publicapi.azurewebsites.net/swagger/#!/Plant/PlantGet
Connects to Isolocity API here:
https://docs.isolocity.com/#operation/parts.store.bulk
On the endpoint enter the consumer key on the apiKey field and submit. This should retrieve back the respective auth_token to use later in the Isolocity integration table.
(Do this for each of the consumer key types)Once you receive the consumer key, visit Dutchie swagger endpoints documentation and look for the “util/AuthorizationHeader..” endpoint
http://leaflogix-publicapi.azurewebsites.net/swagger/#!/Inventory/InventoryReceivedinventoryGet
Connects to Isolocity API here: https://docs.isolocity.com/#operation/receiving-inspections.store
On the endpoint enter the consumer key on the apiKey field and submit. This should retrieve back the respective auth_token to use later in the Isolocity integration table.
(Do this for each of the consumer key types)
Once you receive the consumer key, visit Dutchie swagger endpoints documentation and look for the “util/AuthorizationHeader..” endpoint
http://leaflogix-publicapi.azurewebsites.net/swagger/#!/Vendor/VendorVendorsGet
Connects to Isolocity API here:
https://docs.isolocity.com/#operation/suppliers.store
On the endpoint enter the consumer key on the apiKey field and submit. This should retrieve back the respective auth_token to use later in the Isolocity integration table.
(Do this for each of the consumer key types)
Registering a New Organization to Use the Dutchie Integration
Once you have the Isolocity auth_token, Dutchie consumer keys and auth_token you can add them in the database. This can be done through the following steps:
On integration with Isolocity public api database, open the leaflogix_public_apis table.
Fill in every field respectively:Organization_id: Isolocity Organization id to be integrated
Organization_token: Isolocity token retrieved in “Generate your Dutchie Facility Token for Isolocity API Integration”.
Type: consumer key type (grow or processing)
Auth_token: auth token from Dutchie
Consumer_key: consumer key from Dutchie
After saving, sync of this organization should successfully complete every five minutes.
How Does this Help?
By activating the Isolocity and Dutchie integration, you will be able to import data from various modules in Dutchie.
This includes:
Plant Information (including name and batch number)
Supplier Information (including name)
Receiving Inspections (including parts, batch numbers, quantities, order title, location and suppliers)
The integration will sync information for parts, batch numbers, suppliers and generate receiving inspections as you complete these processes in Dutchie.
This will allow businesses to reduce the double-handling of data and therefore mitigate the risks associated with it.