Operative Media. Operative.One. Release Bulk Data Loaders User's Guide. Document Version 1.0

Transcription

1 Operative Media Operative.One Release Bulk Loaders User's Guide Document Version 1.0 Issued 1/6/2016

2 2016 Operative Media, Inc. All Rights Reserved. This document may not, in whole or in part, be copied, reproduced, translated, or redistributed without the express written consent of Operative Media, Inc. While every reasonable precaution has been taken in the preparation of this document, Operative Media, Inc. cannot guarantee the accuracy of printed or online material after the date of publication. As needed, Operative Media, Inc. will make a reasonable effort to publish updates and revisions to this document and make them available to their customers. 2 Operative.One Release Bulk Loaders User's Guide v1.0

3 Contents Table of Contents About This Document 5 Tell Us What You Think! 5 1 About Bulk Loaders 6 Templates for Bulk Loaders 7 Reference: Template Environments 7 Multiple Object Loaders 8 2 Bulk Loader Reference 9 Accounts and Contacts Loaders 10 Accounts 10 Contacts 13 Production System Account Associations 16 User and Organization Loaders 18 Organizations 18 Users 23 Access Groups 26 Ad Master Model Loaders 29 Ad Slots 29 Ad Slots That Share Inventory 29 Creative Specification Profiles 30 Production System Properties 32 Production System Mapped Values 33 Preset Schedules 35 Product Catalog Hierarchy 37 Standard Products and Ad Slots 37 Syntax: Custom Assignment Statements 44 Package Products 45 Product Ratecard Properties (PRP) 54 Product Cost Method Prices (PCMP) 57 Targeting Options 58 Targeting Premiums 60 Targeting Option Premiums 62 Campaign360 Loaders 64 Primary Line Item to Production Line Item Associations 64 Third Party Delivery Against Primary Line Item Delivery 65 Third Party Delivery Against Sales Line Items 65 Third-Party Associations 65 Operative.One Release Bulk Loaders User's Guide v1.0 3

4 Contents Partner Management Loaders 68 Partners 68 Partner Ad Slots 71 Payment Term Associations 73 Other Loaders 75 Currency Exchange Rates 75 Invoices 75 Sales Order 78 4 Operative.One Release Bulk Loaders User's Guide v1.0

5 About This Document About This Document The User's Guide describes how to use Bulk Loaders in Operative.One Release This publication is intended for all Operative.One customers and partners. Tell Us What You Think! We invite your suggestions, corrections, and comments about the User's Guide: please contact us. Your feedback will help us serve you better. Operative.One Release Bulk Loaders User's Guide v1.0 5

6 Chapter 1: About Bulk Loaders 1 About Bulk Loaders Although almost all objects in Operative.One can be set up by someone using Operative.One's Webbased user interface (sometimes referred to as the UI), for many kinds of objects Operative.One provides bulk data loaders that simplify and expedite initial creation and setup. These loaders let you use Microsoft Excel to define multiple objects at one time. This makes it easier to cut and paste and review details across objects. These loaders are primarily used by Operative personnel to help with your initial implementation. However, administrators at your company may find them useful as well. Some loaders enable you to create and update objects, while others support creation only. This user guide describes most of the bulk data loaders, and provides a link that you can use to download each loader's template file, which you can save and begin populating with object data. In most cases, the objects and columns in loader Excel files correspond to items and fields within Operative.One's Web-based user interface. It is expected that you are familiar with the functionality and fields that appear in the user interface, and that you will be using this bulk data loader documentation together with documentation about the rest of Operative.One. Information about each loader file is in Bulk Loader Reference on page 9, and additional information about the loading process and about many loader file fields can be found where each loader's object is discussed in the Operative.One Administration Module User s Guide. In addition, be aware of the following general concerns: Different levels of error handling are supported with different objects. The Object Import/Export wizard performs some validation and will notify you if there are simple formatting errors, but it does not identify errors after that point. For some types of imports, you may need IDs for related objects. These IDs may be available in reports, the data feed, or in exports when available. When uploading new objects, the ID column should always be left blank so that the system will automatically assign IDs. This will help prevent errors caused by duplicate IDs. There are some data loader fields that support multiple values per record. In those cases, the individual values must be delimited by a semicolon, unless otherwise noted. Most object names are limited to 100 characters for data loading. If you attempt to load in an object with a name of more than 100 characters, it will likely cause an error. The files described in this user guide are those that you load using the Administration module's Object Import wizard, which is described in the Operative.One Administration Module User s Guide. You can import files of sales line items using the Sales module, as described in the Operative.One Sales Module User s Guide; and you can import files using SFTP and FTP, as described in the Operative.One Flat File Production System Integration Guide. This user guide does not address files that are imported via the Sales module, SFTP, or FTP; it addresses only files that are imported using the Object Import wizard. Best practices: It is best to be assigned the support_ops role when you use the loaders. Some options are available only to this role, despite the fact that all options may appear in the drop-down list in the Object Import wizard. 6 Operative.One Release Bulk Loaders User's Guide v1.0

7 Templates for Bulk Loaders Chapter 1: About Bulk Loaders Templates for Bulk Loaders Each bulk data loader has a template defined with the required columns, required formatting, and sample rows. The template is a Microsoft Excel.xls or.xlsx file. You can download a template for most data loaders using the hyperlinks in Bulk Loader Reference on page 9. When you download a template using these links you will need to log on to Operative.One as a user with the support_ops role. In addition to downloading templates using the hyperlinks in Bulk Loader Reference on page 9, templates for some types of objects are available via Operative.One's Web-based user interface, or provided to you directly by Operative. Once you save a template, remove its sample rows, and then populate it with your own data (or edit it if it was an export file already populated with your data). When entering or editing data in a bulk data loader file: The following Excel features are not supported. Avoid them, as they will cause problems when you import a bulk data loader file into Operative.One: hidden columns and rows (all columns and rows will be included in the import) merged cells formulas text formatting (formatting such as bold type and colored text will be ignored) When you copy data into a loader, use Excel's Paste Special feature for either text or values, depending on what you are copying. This removes hidden formatting, formulas, and other features that are unsupported by bulk data loaders. After populating or editing a saved template loader file, you can then import it into Operative.One. Unless otherwise noted, files are imported using Microsoft Excel files (.xls or.xlsx), not straight text (.csv). Reference: Template Environments When you download templates using the hyperlinks in Bulk Loader Reference on page 9, note that there are different Operative.One environments, and you should download templates from the same environment in which you are working. Templates in the production environment are located in: Templates in the staging environment are located in: If you are using a different environment, a corresponding URL should be available to you. The URL will substitute your environment's name for the bold part of the URL in the preceding template locations. Operative.One Release Bulk Loaders User's Guide v1.0 7

8 Chapter 1: About Bulk Loaders Multiple Object Loaders Multiple Object Loaders Some loader files support loading two related objects, such as products and ad slots, and these loaders can establish relationships between them. With these types of data loaders, the following actions are supported for each object type included in the loader: Create adds a new object (product, ad slot, etc.) to the system. Create duplicate adds an object with the same name as an existing object. This action causes the system to skip the lookup and is only supported in certain cases. Update modifies the properties of an existing object and mapping relationship to another object. Map (or empty cell) adds mapping (of one object to another object), but the object properties are not modified. Unmap removes a mapping of an object relationship, but the object properties are not modified. Group maps or unmaps a parent object based on a child object action. Only the access group loader uses this. These keywords may be case sensitive in certain loaders and case may vary. See the notes on individual loaders for details. t all actions are supported for all loaders. 8 Operative.One Release Bulk Loaders User's Guide v1.0

9 Chapter 2: Bulk Loader Reference 2 Bulk Loader Reference The topics that follow describe each data loader and its fields along with any concerns and special instructions. Where applicable, it is a good idea to first review the steps for creating and managing the objects through Operative.One's Web-based user interface, as described in the Operative.One Administration Module User s Guide. Once you are familiar with this, you can work on the bulk creation of many object instances via the loaders. Operative.One Release Bulk Loaders User's Guide v1.0 9

10 Chapter 2: Bulk Loader Reference Accounts and Contacts Loaders Accounts and Contacts Loaders Loaders are available to create and update accounts and contacts. You can also make associations between production system accounts and those within Operative.One. Accounts This loader imports agencies, advertisers, and other accounts. Each row corresponds to an account that appears in the Accounts module. Users with the support_ops role can download the Import_Accounts.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Account from the drop-down list. The following functions are supported: Create Update Be aware of the following considerations when using this loader: Accounts can be optionally associated with each other in a parent/child relationship. To associate a child account (or contact) with a parent account, the parent account must already exist, and it is best to use its Operative.One ID. Therefore, the parent accounts must be loaded first. After those accounts are imported, you can then create child accounts through a second load. Although you can use either IDs or names to associate the accounts, IDs are safer since names are not required to be unique. You may also associate accounts with an external CRM system. However, if you have integrated a CRM system, such as Salesforce.com, with Operative.One, accounts should be maintained in that system and will automatically sync with Operative.One. There are import and export options within the Accounts module as well as the import option in the Administration module. The Import button in the Accounts module is only available to certain roles, and it does not perform all the validations performed through the Administration module. It also does not support updating and will create duplicate accounts when attempting an update. Using this import is not recommended and you should use the Administration module instead. The Export button produces a file that is not immediately importable through the Administration module. You will need to clear out the Parent Account ID and Parent Account Name fields if they appear empty as they may include a hidden character. Also, if multiple industries are assigned to an account, you must change the delimiter to a semicolon to import through the Administration module. You also must remove the contacts and import them separately. The following fields appear in the loader template. 10 Operative.One Release Bulk Loaders User's Guide v1.0

11 Accounts and Contacts Loaders Chapter 2: Bulk Loader Reference Account ID Account Name Account /Syntax Considerations This is the Operative.One ID for the account that is assigned automatically when it is created. When creating a new account, leave this empty and the system assigns an ID. When updating an account, it must be the ID of the existing account, so the system knows which account to update. This is the name of the account as it appears throughout Operative.One. This must be one of the following: Advertiser Integer Update only 11 numbers 255 characters Agency Other You cannot modify this in an update. Status This must be one of the following: Active Inactive Parent Account ID Parent Account Name If this account is the child of another account, this is the ID of the parent account. If the account is not a child, this should be empty. If you export from the Accounts module and wish to import in the Administration module to make changes, a hidden character may appear in this field, even if it appears empty. You will need to manually delete the hidden contents of this field. If this account is the child of another account, this is optionally the name of the parent account. If the account is not a child, this should be empty. You can use either the ID or name to establish the relationship, but the ID is preferred. If you export from the Accounts module and wish to import in the Administration module to make changes, a hidden character may appear in this field, even if it appears empty. You will need to manually delete the hidden contents of this field. Integer 11 numbers 255 characters Phone This is the Phone field for the account. 255 characters Fax This is the Fax field for the account. 255 characters Operative.One Release Bulk Loaders User's Guide v1.0 11

12 Chapter 2: Bulk Loader Reference Accounts and Contacts Loaders Address: Address Line 1 Address: Address Line 2 Address: City Address: State / Province / Region Address: ZIP / Postal Code Address: Country /Syntax Considerations This is the Address Line 1 field for the account. 255 characters This is the Address Line 2 field for the account. 255 characters This is the City field for the account. 255 characters This is the State/Province/Region field for the account. 255 characters This is the Zip / Postal Code field for the account. 255 characters This is the Country field for the account. 255 characters This is the field for the account. The UI ensures this is in the form of an address with and.. However, the loader does not currently enforce this requirement, but you should ensure it is an address for compatibility. 255 characters This is the field for the account. real limit, but too many characters can be problematic for UI. Credit Status This is the Credit Status field for the account. Values depend on what is set up for your company, but must match one of the values you see through the Accounts module UI. By default, it can be one of the following: New account On hold Active client This is case sensitive, matching what you see in the UI. N/A Billing ID This is the Billing ID field for the account. 255 characters 12 Operative.One Release Bulk Loaders User's Guide v1.0

13 Accounts and Contacts Loaders Chapter 2: Bulk Loader Reference Industry Agency Commission Rate CRM System Name External ID /Syntax Considerations This is the Industry field for the account. Values must match industry values already in the system, which are those you see in the UI. Multiple industries must be separated by semicolons. te: The Accounts module export may use commas to separate industries, so you will need to correct this if importing using that export as a source. This is the Agency Discount Rate field for an agency account. If you set this for an account that is not an agency, it is ignored but no error is thrown. Use the integer value not the decimal equivalent (for 25% use 25 not.25). 200 characters Decimal 6 numbers and. decimal indicator. If the account is synchronized with an external system, this is the Name of an external CRM system connection as configured in the Administration module under System > CRM Systems. This must match the name defined in Operative.One if it is used. 100 characters This is typically used as the ID of the account in the external CRM system. 255 characters Contacts This loader imports contact records, and map them to account records. Each row corresponds to a contact that appears on the Contacts tab in the Accounts module. Users with the support_ops role can download the Import_Contacts.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Contact from the drop-down list. The following functions are supported: Create Update Be aware of the following considerations when using this loader: To associate a contact with a parent account, the parent account must be loaded first. After the account exists in the system, you can create contacts for the account using either the account s ID assigned by Operative.One or its name. Using the ID is recommended since names are not necessarily unique. There are import and export options on the Contacts tab within the Accounts module as well as the import option in the Administration module. Operative.One Release Bulk Loaders User's Guide v1.0 13

14 Chapter 2: Bulk Loader Reference Accounts and Contacts Loaders The Import button in the Accounts module is not recommended. Use the Administration module instead. The Export button produces a file that is not immediately importable through the Administration module if contacts have multiple types. To use it, you should cut and paste its contacts rows into the provided sample contacts template using the Paste Special > Values option. If multiple Contact s are assigned to a contact, you must change the delimiter to a semicolon to import through the Administration module. The following fields appear in the loader template. Contact ID Account Name Account ID Operative.One automatically assigns this ID to the contact when it is created. When creating a new contact, leave this empty and the system will assign an ID. When updating a contact, it must be the ID of the existing contact, so the system knows which contact to update. This is the name of the parent account. Although contacts can be imported without accounts, there is normally no reason to do this. To associate a contact with a parent account, the account must already exist in Operative.One. You can use either the ID or name to establish the relationship, but the ID is preferred. You do not need to include both. This is the Operative.One ID of the parent account. Although contacts can be imported without accounts, there is normally no reason to do this. To associate a contact with a parent account, the account must already exist in Operative.One. Associating by the Account ID is recommended, but association by the Account Name is supported if you do not have multiple accounts with the same name. Integer Update only 11 numbers 255 characters Integer 11 numbers 14 Operative.One Release Bulk Loaders User's Guide v1.0

15 Accounts and Contacts Loaders Chapter 2: Bulk Loader Reference Contact This must match a type that appears in the UI which by default is one of the following, unless Operative has made back-end changes: Account Executive Billing Buyer Emergency Primary Production Sales Secondary Technical Traffic Other partner To assign multiple types to a single contact, separate the types by semicolons. This is not case sensitive, but otherwise must match exactly the values in the UI. te: The Accounts module export may use commas to separate accounts, so you will need to correct this if importing using that export as a source. Status This can be one of the following: Active Inactive First Name Last Name This is the First Name of the contact as it appears throughout Operative.One. This is the Last Name of the contact as it appears throughout Operative.One. 100 characters 100 characters Title This is the Title field for the contact. 80 characters This is the field for the contact. The UI ensures this is in the form of an address with and.. However, the loader does not currently enforce this requirement, but you should ensure it is an address for compatibility. 255 characters Phone This is the Phone field for the contact. 255 characters Operative.One Release Bulk Loaders User's Guide v1.0 15

16 Chapter 2: Bulk Loader Reference Accounts and Contacts Loaders Mobile This is the Mobile field for the contact. 255 characters Fax This is the Fax field for the contact. 255 characters Address: Address Line 1 Address: Address Line 2 Address: City Address: State / Province / Region Address: ZIP / Postal Code Address: Country This is the Address Line 1 field for the contact. 255 characters This is the Address Line 2 field for the contact. 255 characters This is the City field for the contact. 255 characters This is the State/Province/Region field for the contact. 255 characters This is the Zip / Postal Code field for the contact. 255 characters This is the Country field for the contact. 255 characters This is the field for the contact. real limit, but too many characters can be problematic for UI. CRM System Name External ID If the contact is synchronized with an external system, this is the Name of an external CRM system connection as configured in the Administration module under System > CRM Systems. This must match the name defined in Operative.One if it is used. This is typically used as the ID of the contact in the external CRM system. 100 characters 255 characters Production System Account Associations This loader manages the associations between Operative.One accounts and corresponding accounts in primary production systems. This associating is normally made automatically when orders are pushed or delivery data is pulled and associated with production line items. Through the loader, you can make these 16 Operative.One Release Bulk Loaders User's Guide v1.0

17 Accounts and Contacts Loaders Chapter 2: Bulk Loader Reference associations in bulk. This simplifies the Ad Operations module push process because new tickets for an Operative.One advertiser will automatically show the production system account as an option. Users with the support_ops role can download the Import_Production_System_Account_Associations.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select PS Account Associations from the drop-down list. The following functions are supported: Map Unmap Be aware of the following when using this loader: Production system accounts must be loaded (pulled) into Operative.One before associations are made through this loader. The PS Customer Id is used only for AdTech production systems. A PS Customer cannot be included unless a PS Advertiser is also included. At this time, the PS IDs are actually Operative.One IDs assigned to the imported record from the production system. Operative will need to provide mappings between these IDs and those in your production system for you to use this loader until this is changed. The following fields appear in the loader template. Account Id This is the Operative.One ID for the account. It must be an advertiser account. Production System Id Action PS Advertiser Id PS Customer Id This is the Operative.One ID for the production system connection defined in the Administration module under Ad Master Model > Ad Operations > Production Systems. This must be either Map or Unmap. Map makes an association between the Operative.One advertiser and the production system advertiser. Unmap removes an association. Integer Integer This is currently the Operative.One ID for the production Integer system advertiser record. It is not currently the ID from the production system. Operative will need to provide mappings between these IDs and those in your production system for you to use this loader until this is changed. This is currently the Operative.One ID for the production system customer record for AdTech systems only. It is not currently the ID from the production system. 11 numbers 11 numbers 6 characters Integer 11 numbers 11 numbers Operative.One Release Bulk Loaders User's Guide v1.0 17

18 Chapter 2: Bulk Loader Reference User and Organization Loaders User and Organization Loaders Loaders are available to create the organization hierarchy and users within Operative.One. This mostly corresponds to configurations available in the Administration module on the System tab. Organizations This loader imports and modifies business entities, partners, media properties, teams, and approval groups in the organization hierarchy. It sets up the organizations in the Administration module under System > Organizations > Organizations. Users with the support_ops role can download the Import_Organizations.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Organization from the drop-down list. The following functions are supported: Create Update Be aware of the following when using this loader: The top of the organization hierarchy always has ID 1 and is created by default when Operative.One is set up for your company. By default this is named Global Default Organization, and it has the type Global Organization. It cannot be removed or moved within the hierarchy. It should not be made inactive. However, it can be renamed. It is best to edit this global organization through the UI rather than a loader. Parent and child organizations cannot be created through the same upload. You must create the parents first either through a separate import or through the UI. The system does not prevent you from having different organizations with the same name as long as they are not the same type or level. For example, Operative can be the name of a business entity and a media property, but you cannot have two or more Operative media properties. However, multiple teams can have the same name, but not under the same parent. However, all of this is highly discouraged. Although the system does not prevent duplicate names, it is not recommended. t all areas of the system make it clear where in the hierarchy the organization belongs or what type of organization it is. Therefore, in many places, you would see the same name repeated without a clear indication as to where or what it is. Whenever possible, avoid having organizations with the same name, even if they are different types. This loader can import partner users and assign them to partner organizations. This is only used for partner users as the only role assigned to the user will be Partner. While you can add partners using this data loader, using the Partner data loader instead is recommended if you plan to add partner users. The partner specific data loader is better for associating one or more (external) partner users directly with that partner, thereby granting them access to that partner within the Partner Central module. The following fields appear in the loader template. 18 Operative.One Release Bulk Loaders User's Guide v1.0

19 User and Organization Loaders Chapter 2: Bulk Loader Reference Organization This should be left empty. It is not needed. ID To update an organization, this must be the ID assigned by Operative.One when the organization was created. It must be empty for a create. Integer Update only Name This is the name of the organization. 50 characters This must be one of the following: Media Property Approval Group Partner Team Partner Business Entity Parent Id This is the ID of the organization above this organization in the hierarchy. This parent organization must already exist. The parent and child cannot be created in the same import. You can identify the parent by using either this ID or the name in the next column. Parent Name This is the name of the organization above this organization in the hierarchy. This parent organization must already exist. The parent and child cannot be created in the same import. You can identify the parent by using either the name or the id in the previous column. Parent This identifies the type of parent organization and must be one of the following, matching the parent s type: Global Organization Integer Approval Group Partner Team Partner Business Entity Status This must be one of the following (case sensitive): active inactive This is the address for the organization. It must be in the form of an address with and.. 50 characters Operative.One Release Bulk Loaders User's Guide v1.0 19

20 Chapter 2: Bulk Loader Reference User and Organization Loaders Phone This is the Phone field for the organization. 25 characters Fax This is the Fax field for the organization. 25 characters Billing Address: Address Line 1 Billing Address: Address Line 2 Billing Address: City Billing Address: State / Province / Region Billing Address: ZIP / Postal Code Billing Address: Country Shipping Address: Address Line 1 Shipping Address: Address Line 2 Shipping Address: City This is the Billing Address: Address Line 1 field for the organization. The next five columns correspond to the other billing address fields. The column headers match their UI names. This is the Shipping Address: Address Line 1 field for the organization. The next five columns correspond to the other shipping address fields. The column headers match their UI names. 255 characters 255 characters 25 characters 50 characters 25 characters 25 characters 255 characters 255 characters 25 characters 20 Operative.One Release Bulk Loaders User's Guide v1.0

21 User and Organization Loaders Chapter 2: Bulk Loader Reference Shipping Address: State / Province / Region Shipping Address: ZIP / Postal Code Shipping Address: Country Pub Code Memo Site URL Production Systems FirstName This is a free text entry field for media properties and business entities. It is not visible for the other organizations, so should not be loaded for them. te: The loader allows you to load a value for other organizations, but this is not recommended. This is a free text entry field for business entities. It is not visible for the other organizations, so should not be loaded for them. te: The loader allows you to load a value for other organizations, but this is not recommended. This is a free text entry field for media properties and partners. It is not visible for the other organizations, so should not be loaded for them. te: The loader allows you to load a value for other organizations, but this is not recommended. For media properties only, this identifies the primary publisher production system that serves content for the media property. It must match the name of a system defined in the Administration module under Ad Master Model > Ad Ops > Production Systems. To associate multiple systems, separate their names by semicolons. For partner organizations only, this sets the first name of a partner user. Through the loader, you can create a user that is associated with the partner. This user has the Partner role. These are the users you can create in the Partner360 module. If you specify any of the user fields in the loader, you must specify all six of them. 50 characters 25 characters 50 characters 20 characters 150 characters unless importing a user 50 characters Operative.One Release Bulk Loaders User's Guide v1.0 21

22 Chapter 2: Bulk Loader Reference User and Organization Loaders LastName UID Password Status For partner organizations only, this sets the last name of a partner user. For partner organizations only, this sets the address of a partner user. For partner organizations only, this sets the login name of the partner user. On an update, if this is an existing login name, the user is updated. This should not include portion of the name. For partner organizations only, this sets the password associated with the UID. For partner organizations only, when specifying a user, this must be one of the following (case sensitive) for the user: active inactive unless importing a user unless importing a user Integer unless importing a user unless importing a user unless importing a user 50 characters 50 characters 50 characters (but must account portion) Rate Card Header HTML For business entities only, this associates a rate card. It must match the name of a rate card defined in the Administration module under Ad Master Model > Sales > Rate Cards. To associate more than one rate card, separate names by a semicolon. te: This association is not enforced or defaulted anywhere. For business entities only, this associates a header. It must match the name of a header defined in the Administration module under Module Settings > Sales > Headers. To associate more than one header, separate names by a semicolon. te: This association is not enforced or defaulted anywhere. 22 Operative.One Release Bulk Loaders User's Guide v1.0

23 User and Organization Loaders Chapter 2: Bulk Loader Reference Terms and Conditions Primary Contact Manager Payment Terms Monthly Impression Quota For business entities only, this associates terms and conditions. It must match the name of terms defined in the Administration module under Module Settings > Sales > Terms & Conditions. To associate more than one, separate names by a semicolon. te: This association is not enforced or defaulted anywhere. This sets a partner user associated with a partner, media property, or business entity. It must be the first name and last name of an Operative.One user with the Partner role that is associated with a partner organization. It is not applicable for a team or approval group. For a partner only, this sets the user responsible for managing the partner relationship. It must be the first name and last name of an Operative.One user with the Partner Manager role. For partners and media properties, this sets payment terms that determine how partner payments are calculated. It must match the name of payment terms defined in the Partner360 module. It is required for a partner, optional for a media property, and not allowed for other organizations. For a partner only, this sets the impression quota that appears on a partner s Performance tab in the Partner360 module. Integer for partners only Users This loader is used to add users to the system and to set their security, team, and other attributes. Users with the support_ops role can download the Import_Users.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Security User from the drop-down list. The following function is supported: Create Be aware of the following when using this loader: Operative.One Release Bulk Loaders User's Guide v1.0 23

24 Chapter 2: Bulk Loader Reference User and Organization Loaders The team fields are optional. If these are left blank, the user is associated with the default global team. Users with the same name but different UIDs can be created. Hyphens in the UID field are NOT supported. Multiple roles must be separated with semicolons with no spaces. The following fields appear in the loader template. User This is reserved for future functionality and should be left empty. FirstName This is the first name of the user. LastName This is the last name of the user. UID Password This is the address of the user. This is required and the row will not import if this is not in the form of a valid address. For example, it must have symbol and cannot have characters not allowed in most addresses. At this time, the validation phase of the importer may not indicate errors with the address, so be sure to confirm it before importing. This is the login ID that lets the user access Operative.One. This must be unique per user. If a row has an ID for an existing UID, it is not loaded. Update is not supported through this loader at this time. It is best not to include portion that identifies you company s environment (tenant) within Operative.One. That portion of the ID is assign automatically if it is not included. At this time, the validation phase of the importer may not indicate errors if you try to load a row with an existing UID. This is the password to let the user log in to Operative.One. It must be at least 8 characters. A row will not import if it has a password with less than 8 characters, although it will import for a row without a password. At this time, the validation phase of the importer may not indicate errors with the password, so be sure to confirm all rows have at least 8 characters before importing. The loader will allow you to import passwords that are less strict than what the UI enforces, but still requires 8 characters. 24 Operative.One Release Bulk Loaders User's Guide v1.0

25 User and Organization Loaders Chapter 2: Bulk Loader Reference Status This must be one of the following: active inactive Roles HomeTeamId This indicates the user s roles. A user must have at least one role. Multiple rows must be separated by semicolons. The names here must match those shown in the UI when defining a user. For example: ad_master; adops_manager; api_only; auditor; billing_analyst; campaign_manager; credit_ status_manager; finance_manager; outsourced_ trafficker; partner; partner_manager; payment_analyst; payment_proc; perf_analyst; report_creator; sales_admin; sales_ae; sales_ approval_admin; sales_approver; sales_full; sales_planner; support_ops; trafficker; user_ administrator This is the Operative.One ID for the user s home team organization. If this is empty, the loader uses the HomeTeamName. If HomeTeamName is also empty, the global default team is used. te: Be sure the ID is the ID of a team organization and not one of the other types (business entity, approval group, etc.). For most other types, the row will not import but for approval groups it will be erroneously assigned as the home team. HomeTeamName This is the name of the user s home team. This is ignored if HomeTeamId has a value. If HomeTeamName and HomeTeamId are both empty, the global default team is used. Access Group Action Access Group ID Access Group Name Address 1 te: Be sure to specify a team organization and not one of the other types (business entity, approval group, etc.). For most other types, the row will not import but for approval groups it will be erroneously assigned as the home team. This is reserved for future functionality and should be left empty. This is reserved for future functionality and should be left empty. This is reserved for future functionality and should be left empty. This is the first line of the user's street address, and can be up to 250 characters. Integer Operative.One Release Bulk Loaders User's Guide v1.0 25

26 Chapter 2: Bulk Loader Reference User and Organization Loaders Address 2 This is the second line of the user's street address, and can be up to 250 characters. City This is the user's city, and can be up to 250 characters. State This is the user's state, province, or region, and can be up to 250 characters. Zip This is the user's postal code, such as a ZIP code, and can be up to 20 characters. Country This is the user's country, and can be up to 250 characters. Phone This is the user's primary phone number, and can be up to 20 characters. Mobile This is the user's mobile phone number, and can be up to 20 characters. Fax This is the user's fax number, and can be up to 20 characters. Access Groups This loader creates and updates access groups and as well as maps or unmaps products with groups. You can manage access groups and their hierarchy in the Administration module under System > Security > Access Groups. At the top of the hierarchy is the default access group which is linked to the global default team for your organization. All newly created products are automatically linked to this default access group, and the products in this top access group are available to all groups. If your organization does not limit which users sell which products, you can leave this default and all users can sell all products. If you want to limit which users can sell which products, you must remove (unmap) products from the default access group and associated them with other access groups as needed. te: A product can belong to multiple access groups. Therefore, be careful when mapping and unmapping to ensure products are only in the appropriate groups. te: At this time, you cannot directly associate or unassociate users from access groups. Users with the support_ops role can download the Import_Access_Groups.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Access Group from the drop-down list. The following functions are supported: Create Update Group 26 Operative.One Release Bulk Loaders User's Guide v1.0

27 User and Organization Loaders Chapter 2: Bulk Loader Reference Map Unmap The following fields appear in the loader template. Access Group ID Access Group Action Name Parent ID Parent Name Status This is the ID assigned by the system when the group is created. It should be empty when creating a group but must be provided when performing any other action. This can be one of the following: Create adds a new access group to the system. Update modifies fields of an existing group. Group does not modify group fields but will map and unmap products. For this, you only need to identify the Access Group ID and the last three product columns. This is the name of the group. It is required for an Update or Create action and optional for a Group action. This is the ID of the access group under which the group appears. Either this or Parent Name is required. This is the name of the access group under which the group appears. Either this or Parent ID is required. This sets whether the group is in use and must be one of the following: Active Inactive Integer 50 characters 50 characters This is the optional field for the group. This is the optional field for the group. 50 characters Product Action This can be one of the following: Map adds a product to the access group. Unmap removes a product from the group. Product ID Product Name It can also be empty if the Access Group Action is not Group. This is the ID of the product you wish to map or unmap. You can specify the product using either this or the Product Name. This is the name of the product you wish to map or unmap. You can specify the product using either this or the Product ID. Integer Operative.One Release Bulk Loaders User's Guide v1.0 27

28 Chapter 2: Bulk Loader Reference User and Organization Loaders 28 Operative.One Release Bulk Loaders User's Guide v1.0

29 Ad Master Model Loaders Chapter 2: Bulk Loader Reference Ad Master Model Loaders Loaders are available to set up and maintain objects configured in the Administration module on the Ad Master Model tab. These objects set up what is produced and sold. Ad Slots You can create ad slots by using the Product / Ad Slot loader and omitting the product information. The same file is used to define ad slots on their own or ad slots with products. For more information about using the Product / Ad Slot loader, see Standard Products and Ad Slots on page 37. Ad Slots That Share Inventory This loader establishes relationships between ad slots that have overlapping inventory for use with the Operative.One inventory manager. For example, different DFP ad sizes may require part of or all of the same space on a page, and therefore impact the same pool of available impressions. This loader lets you identify ad slots that should book the same inventory even when their locators are not the same and they do not have a hierarchical relationship. Users with the support_ops role can download the Import_Ad_Slots_That_Share_Inventory.xlsx sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Ad Slots That Share Inventory from the dropdown list. The following function is supported: Map (inherent) Be aware of the following when using this loader: This loader provides a row in which you identify the two ad slots by their names. The relationship is established in both directions. If you have a row for AdSlot_A, AdSlot_B, then you do not need a row for AdSlot_B, AdSlot_A. The AdSlot_B, AdSlot_A association is created automatically. When you associate two ad slots, associations are also established between any ad slots associated with either of the ad slots. For example, if you have a row for AdSlot_A, AdSlot_B then a row for AdSlot_B, AdSlot_C, the system automatically creates the AdSlot_A, AdSlot_C association. You can only establish relationships between ad slots for the same production system. The associations do not affect Direct to DFP or external (Yieldex) inventory. The following fields appear in the loader template. Ad Slot Name Ad Slot Name This is the name of an ad slot that shares inventory with another ad slot. This is the name of the ad slot that shares inventory with the first column ad slot. 100 characters 100 characters Operative.One Release Bulk Loaders User's Guide v1.0 29

30 Chapter 2: Bulk Loader Reference Ad Master Model Loaders Creative Specification Profiles This loader is used to import creative specification profiles that are later associated with products. These can be created in the Administration module, under Ad Master Model > Sales > Creative Specs. Each row in the file corresponds to one specification. Users with the support_ops role can download the Import_Creative_Specification_Profiles.xls sample template from the templates directory introduced in Template Environments on page 7. To import the completed loader into Operative.One, go to the Administration module > System tab > Categories > Tools > Object Import/Export, and select Creative Specs Profile from the drop-down list. The following functions are supported: Create Update Be aware of the following when using this loader: You can access an empty loader template using the Download Template button in the upper right of the Creative Specs page in the Administration module. You can use this or the version with sample rows available through the special templates link. This file contains two header rows, one for digital specs and one for print. The columns vary depending on the type. If you are not importing for both, you can remove the header for the one you are not using. You can import both within the same file, but it is easier to import them in separate files. Most fields are not validated for their input other than some requiring numbers and some allowing free text. The purposes and requirements for these fields vary depending on the production system and your business rules. In some cases, when uploading to update, the validation message may say that there were errors, but the upload will still update rows. The following columns appear for both digital and print specifications. Id Name This is the ID assigned by Operative.One when the creative spec profile is created. When creating a new spec, leave this empty and the system will assign an ID. When updating a spec, it must be the ID of the existing spec, so the system knows which spec to update. This is the name of the creative specification as it appears throughout Operative.One. Required Integer Update only This is the field for the creative spec. Media This must be one of the following: Digital Print Different columns apply depending on this choice. 30 Operative.One Release Bulk Loaders User's Guide v1.0

31 Ad Master Model Loaders Chapter 2: Bulk Loader Reference Primary Measurement Unit Width Height This is the measurement used for the width and height fields that follow. Some common measures include px, mb, kb, cm, or in, but no validation is performed on this field. This is the width of the creative (in-banner, unexpanded) using the measure above. This is the height of the creative (in-banner, unexpanded) using the measure above. Required Integer Integer The following columns appear only for Digital specifications. Refer to the Operative.One Administration Module User s Guide for descriptions of the fields. The only validations performed by the loader are related to data type. Required Expanded Height Integer Expanded Width Integer Allowed Expanded Directions HTML Max Code Size Integer Max Initial Load File Size(k) Integer Max File Size Flash / Rich Media(k) Integer Max File Size GIF/JPG(k) Integer Max File Size tes Integer Max Anim. Time(s) Integer Max FPS Integer Max Animation Loops Integer Ad Integer Broadband Min Time(s) Integer Broadband Max Time(s) Integer Broadband Format Integer Broadband Preformatted Integer Broadband Clickable Integer Broadband Companion Ads Integer Alt Max Chars Integer Third Party Tags Accepted Third Party Tracking Accepted Sound Allowed Max Creatives Per Campaign (image rotation) Integer Operative.One Release Bulk Loaders User's Guide v1.0 31