dbo.Customers
Field | Data Type | Description |
BaseScenario* | Text | Base scenario name |
Customer* | Text | Customer name, e.g. “RTL_Kroger_600_IL_Chicago” |
CustomerDescription | Text | Customer description |
City | Text | City |
State | Text | State or province abbreviated, e.g. "GA" |
Country | Text | Country |
PostalCode | Integer | Postal Code |
Latitude | Float | Latitude - Must be populated for Mapping to work correctly. Can be auto-populated by Geocoding Data Assistance Tool. |
Longitude | Float | Longitude - Must be populated for Mapping to work correctly. Can be auto-populated by Geocoding Data Assistance Tool. |
GeocodeMethod | Text | When using Geocode in Architect, this field will auto-populate with the sole Geocode method that Gains uses, “AzureMaps" |
Prefix | Text | Customer prefix. It is used for convenience in filtering and/or reporting, e.g. “RTL” for the example customer “RTL_Kroger_600_IL_Chicago” |
Notes | Text | Freeform notes |
SolverInclude* | Text [Yes, No] | Indicates whether this record is active |
If the address fields are filled out but the latitude and longitudes coordinates are not, use the architect geocoding tool to populate these two fields.
We need to do this because the COG Solver relies on the lat/long coordinates of customer locations to decide on new location(s) for manufacturing and/or distribution centers.
If the latitude and longitude coordinates are filled out but the address fields are not, this approach will work. However, we recommend using the reverse geocoder to populate the address fields.
This method will display the address in the output, which users are generally more familiar with.