Columns in the Object Import file and possible Error/Warnings
Columns in the object import file:
Object number: If the field is required or not depends on the setting autogenerate object numbers. Id of the object in the system. Can be numbers, letters and hyphens. This should be a new unique number for importing new objects, or an existing object number when updating already existing objects.
Group: Required field. Name of the object group. Object group must exist in the system in order to go through with the import.
Status: Optional field. Status of the object. If left blank the object will be imported as active. Valid values are active, inactive or deployment. This status determines if the object is deliverable (active), not deliverable (inactive) or in deployment (deployment). Orders can still be placed on inactive objects but the orders will not be activated until the status has been changed to active.
Drop installed: If the Object has been deployed or not (Yes/No). Will be changed to Yes when submitting tasks with Task type Drop installation.
Active from: Optional field. Date when the object should be activated (it’s possible to place orders on the object). If left blank, the date will be set to yesterday.
Street: Optional field. The street address where the object is located.
Street number: Optional field. The street number where the object is located.
State/Province: Optional field. State or Province where the object is located.
Unit number: Optional field. The unit/apartment number for the object.
Postal/ZIP code: Optional field. Zip code for where the object is located.
City: Optional field. City where the object is located.
Object owner: Optional field. The name of the company or organization owning the object. If left blank the owner will be set to Default. If the entered owner does not exist the owner will be created. Only shown if the object owner feature is enabled.
Object type: Optional field. The name of the object type. If left blank the type will be set to Default. If the entered object type does not exist it will be created.
Searchable in the Customer portal: Optional field. Controls if the object should be found in the Marketplace when a customer searches for their address (mostly used in non-provisioned networks but also in provisioned networks with address search). Possible values are disabled, searchable, searchableandorderable, searchable and orderable in deployment or inherit. Read more about the different values here. If left empty, inherit will be set.
Note: Optional field. Internal note about the object. Only visible for the operator. Don’t wrap the text.
Public note: Optional field. Note that will be visible for both Operators and Service providers. Don’t wrap the text.
Latitude: Latitude for the location. Format example 38,4582266
Longitude: Longitude for the location. Format example -122,7107917
Validated: If the address should be validated against Google or not. If Yes/True/1, the address will not be validated. If the address should be validated towards Google, set the value to No/False/0.
Country: Optional field. Country where the object is located.
Parent object: Only required if the Object type is a "Unit"
Error/Warnings:
Missing object owner, will be set to default object owner: If no object owner is entered, default will be used.
Could not find object owner, will be created when imported: If another name than a registered object owner is entered, the object owner will be created.
Could not find object type, will be created when imported: If another name than a registered object type is entered, the object type will be created.
No searchable for object, will be imported as inherit: Shown if no value is entered in the Searchable in the customer portal column. Read more about the column above.