Import-NectarLocations
- 15 May 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Import-NectarLocations
- Updated on 15 May 2023
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Imports a CSV list of locations into Nectar DXP
Description
Import a CSV list of locations into Nectar DXP. This will overwrite any existing locations with the same network ID. Useful for making wholesale changes without wiping and replacing everything.
Assumes you are working from an export from the existing Nectar DXP location list.
Syntax
Import-NectarLocations
-Path <String>
-TenantName <String>
-SkipGeoLocate
Parameters
-Path <String>
The path to the CSV file to import into Nectar DXP. The CSV file must use the standard column heading template used by Nectar DXP exports.
| Parameter | Value |
|---|---|
| Required | true |
| Position | 1 |
| Required | true |
| Default Value | None |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-TenantName <String>
The name of the Nectar DXP tenant. Used in multi-tenant configurations.
| Parameter | Value |
|---|---|
| Required | false |
| Position | 2 |
| Required | false |
| Default Value | None |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
-SkipGeoLocate <SwitchParameter>
Don't attempt geolocation. Do this if you don't have a valid Google Maps API key or the lat/long is already included in the CSV.
| Parameter | Value |
|---|---|
| Required | false |
| Position | named |
| Required | false |
| Default Value | False |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
Was this article helpful?