Importing Data with Data Loader In a Nutshell The following document describes the process for importing data using the Data Loader. The Data Loader is located at Master Data Management > Settings > Data Loader. Data Loader Templates The Data Loader Templates are used to upload data managed in other systems to the Coresystems Cloud for use in the Field Service Management applications. The fields contained in the template references correspond to the column names used in the Coresystems Cloud Data Model. The id columns may refer to: the externalId property supported in version 4 of the Data API the code property (generally specific to ERPs) or to name property, or even to userName/emailAddress. This column is used to connect data objects to one another. For example, a Contact record could specify the id of a Business Partner, which would then connect the Contact to the Business Partner. Note: For more information on the Data Objects supported by the Data Loader (including constraints, types, and categories), refer to the Data Object table below. Template Field Reference Select the data object template you would like to learn more about from the header row below. You can then toggle between data object templates to view how connections can be made between them using the id field. Note: All required data template columns are indicated by an asterisk (*). All unrequired columns can be removed if not needed for data import. Address Business Partner Business Partner Group Contact Equipment Item Payment Term Payment Type People Price List Shipping Type Skills Project Project Phases Activities People - Skills Assignment Address Template Field Description block If applicable. The block associated with the address. building If applicable, the building associated with the address. city The city in which the address is located. country The country in which the address is located. county If applicable, the county or regional unit in which the address is located. defaultAddress Used to indicate if the address is the default. floor The floor on which the address is located. id* Required. The unique ID associated with the address. This ID is used to connect the address record to another record type, such as a BUSINESSPARTNER. name The name of the address. name2 If appliable, a second or alternative name. name3 If applicable, a third or second alternative name. object.objectId The object ID that the address refers to (example: the code associated with the BUSINESSPARTNER.) object.objectType The type of object to which the address references (i.e. BUSINESSPARTNER, if the address is for a BUSINESSPARTNER). postOfficeBox The Post Office Box numer (PO Box) associated with the address. remarks Remarks or notes related to this address, can be used for any string based content which contains necessary information. room If applicable, the room in which the address is located. state If applicable, the state in which the address is located. street The name of the street on which the address is located. streetNo The street or house number associated with the address. type The type of address used to categorize the address (example: shipping, billing, default, etc). zipCode If applicable, the ZIP Code associated with the address. Business Partner Template Field Description additionalName The additional name for this business partner. city The city of the main address of this businesspartner (used to search and display in list) -> may overlap with the default address city. code System code of this object, normally this correlates to the erp id given by the source system. country The country associated in which the main address of the Business Partner is located. creditLimit.amount The credit limit of this businesspartner, specified as a monetary amount to be most precise and formattable. creditLimit.currency The currency associated with the credit limit. currency Currency of this business partner. Business partners that have multiple currencies are indicated by not assigning any currency. emailAddress The public email address. fax The fax machine number. groupCode The code of the group which the business partner belongs to. This must be a value which is also present in the BusinessPartnerGroup model. groupName The name of the group which the business partner belongs to. This must be a value which is also present in the BusinessPartnerGroup model. id* The unique ID of the business partner. language The default language settings value when an offline reports is generated on the client. mobilePhone The mobile phone. name The name of the business partner. officePhone The office phone number. otherPhone If applicable, another phone number associated with the business partner. password The business partner password. paymentTerm Associated payment term. paymentType Link to default payment type. priceList Specifies the pricelist assigned to this businesspartner. The pricelist is used during creation of sales orders, materials and other objects which allow to choose items to calculate the prices. Business Partner Group Template Field Description businessPartnerCode The code associated with the business partner. id* The unique ID associated with the business prtner group. name The name of the business partner group. Contact Template Field Description birthDate The birth date of the contact. code System code of this object, normally this correlates to the ERP id given by the source system. defaultContact Indicates if this is the default contact of a business partner. emailAddress The email address of the contact. fax The fax machine number. firstName The first name of the contact. gender The gender of the contact. id* Required. The unique ID associated with the contact. lastName The last name of the contact. mobilePhone The mobile phone number. object.objectId The ID of the object to which the contact information refers to (i.e. a specific BUSINESSPARATNER). object.objectType The type of object which the object references (e.g. a BusinessPartner if this is a BUSINESSPARNTER contact). officePhone The office phone. otherPhone If applicable, another phone. pager If applicable, the pager number. positionName The name of the contact's position. profession The name of the contact's profession. remarks Any remarks related to the contact. remarks2 Additional remarks related to the contact. skypeName The skype name/ID of the contact. title The title of the contact. Equipment Template Field Description businessPartner Business partner reference to which this equipment belongs. code System code of this object, normally this correlates to the erp id given by the source system. contact Responsible contact person on business partner side. globalUniqueId Global unique (in the cloud scope) equipment identifier. id* The unique ID associated with the equipment record. item Indicates which item this equipment represents. manufacturerSerialNumber Serial number of the item (equipment) manufacturer. name Name of the equipment at customer side. parentId References a parent equipment for this one. remarks Remarks or notes of this equipment, can be used for any string based content which contains necessary information. serialNumber The serial number of this specific equipment (may be identical to manufacturer serial number in some cases). serialNumber2 Indicates which item this equipment represents. status Status of the equipment. type Type of the equipment. udf If applicable, any User-defined field associated with the equipment record. NEW1[float] Item Template Field Description code.groupCode System code of the assigned ItemGroup's object. groupName System name of the assigned itemGroup's object. id* Required. The unique ID associated with the item record. inventoryItem Indicates if this item is an inventory item mangedByBatches Indicates that the item is managed by batches. managedBySerialNumbers Indicates that the item is managed by serial numbers. name Display name of the item. nameTranslations If applicable, the displayed translation name of the item. ordinal Ordinal number of the item. properties Additional properties to detailed specify the item and its properties purchaseItem Indicates if this item can be used for purchase orders. remarks Remarks or notes of this item, can be used for any string based content which contains necessary information. salesItem Indicates if this item can be used for sales documents. serialNumberItem Indicates if this item can have serial numbers assigned. typeCode System code of the assigned ItemType's object. typeName System name of the assigned ItemType's object. unitofMeasure Unit of measure used for this item. Payment Term Template Field Description code.id* System code of this object, normally this correlates to the erp id given by the source system. name Display name of this object. priceList Pricelist associated with this payment term. Payment Type Template Field Description businessPartnerType Indicates the BusinessPartnerType. code.id* System code of this object, normally this correlates to the erp id given by the source system. name Display name of this object. type Type of this payment. Person Template Field Description address Address of the person. branchCode System code of the employee branch object. branchName System name of the employee branch object. code System code of this object, normally this correlates to the erp id given by the source system. departmentCode System code of the employee department object. departmentName System name of the employee department object. emailAddress Email address. externalResource Indicated whether the resource is external. fax The fax number associated with the person receord. firstName The first name of the person. homePhone The home phone number of the person. id* The unique ID associated with the person record. jobTitle The job title of the person. lastName The last name of the person. locationLastUserChangedDate Required to know when the person location has been last time updated. loginEnabled Flag used to indicate if we have a cloud user (user account) created on MC for this person. Is applicable only for persons of type PersonType.ERPUSER manager References the person of PersonType.EMPLOYEE which is the manager of this person. mobilePhone Mobile phone. officePhone Office phone. otherPhone Mobile phone. officePhone Office phone. mobilePhone Mobile phone. pager Office phone. personStatus Mobile phone. plannableResource Office phone. positionCode Mobile phone. positionName Office phone. refId Unique identifier of the physical representation multiple person objects. See header for more information. remarks Remarks or notes of this activity, can be used for any string based content which contains necessary information. skills String field which contains a persons skills in specific areas (plaintext field) skypeName The account name of the Skype service. Type Type of this person object. userName The user name of the person in the backend system. Price List Template Field Description code System code of this object, normally this correlates to the erp id given by the source system. id* Required. The unique ID associated with the price list. name The price list display name. Shipping Type Template Field Description code System code of this object, normally this correlates to the erp id given by the source system. id* Required. The unique ID of the shipping type record. name TThe display name of the shipping type. Skills Field Description name* Required. The name of the skill. description A description of the skill. Project Field Description id* Required. The unique ID of the project subject* Required. The subject of the project. This is used as the project name. code* The code associated with the project. projectType* Required. The type of project used to categeorize the project. description A description of the project. responsiblePersonId The ID of the person responsible for the project. equipmentId* Required. The unique ID of the equipment associated with the project. businessPartnerId* The unique ID of the Business Partner (customer, vendor, etc) associated with the project. owners(split separator '|') The project owner/s associated with the project. The vertical separator ( | ) is used when there are more than one owner. The field might be later used to set up correct permissions, e.g. you can set up that only a project owner can modify a project with which they are set as an owner. contact.firstName The first name of the project contact. contact.lastName The last name of the project contact. contact.title The title of the contact (example: Dr., Mr., Mrs.) contact.positionName The position of the contact (example: manager). contact.profession Required. The profession of the contact. contact.emailAdress* Required. The email address of the contact. contact.mobilePhone The mobile phone number of the contact. contact.officePhone The office phone number of the contact. contact.otherPhone An additional or unspecified phone number of the contact. contact.pager The pager number of the contact. contact.fax The fax number of the contact. contact.skype The skype ID of the contact. contact.gender The gender of the contact. contact.remarks Internal remarks associated with the contact (example: do not disturb before 9 AM). Project Phases Field Description id* Required. The unique, external ID of the project phase. name* Required. The name of the project phase. parentPhaseId If the project phase is connected to another project phase, the ID of the parent phase. projectId* Required. The ID of the project to which the project phase belongs. projectOrdinal Only even numbers without 0. This field is responsible for the correct Activities order in the Project Management app. owners(split separator '|') The project owner/s associated with the project. The vertical separator ( | ) is used when there are more than one owner. The field might be later used to set up correct permissions, e.g. you can set up that only a project owner can modify a project with which they are set as an owner. Activities Field Description id* Required. The unique, external ID of the activity. businessPartnerId The ID associated with the business partner for whom the activity occured. checkedOut True or false. True means that the activity was successfully checked out. endDateTime The date/time on which the activity ended. equipmentId The ID of the equipment associated with the activity. number The number associated with the activity. personal True of false. True indicates that the activity is Personal. previousActivityId If applicable, the previous ID associated with the activity. This number may have been generated in another system. remarks The remarks associated with the activity (example: important activity). reminderDateTime The date/time at which a reminder was sent to the employee assigned to the activity. startDateTime The date/time on which the activity began. Status The status of the activity. Subject The subject of the activity. This value is used as the name of the activity. type The type associated with the activity (example: assignment). projectOrdinal Only even numbers without 0. This field is responsible for the correct Activities order in the Project Management app. owners(split separator '|') The project owner/s associated with the activity. The vertical separator ( | ) is used when there are more than one owner. The field might be later used to set up correct permissions, e.g. you can set up that only an activity owner can modify an activity when they have been set as an owner. address.name* Required. The name of the address at which the activity occurred. address.name2 If applicable, the name of the second address associated with the activity. address.name3 If applicable, the name of the third address associated with the activity. address.street The street address associated with address.name. address.streetNo The house number or building number associated with address.name. address.zipCode The zip code associated with address.name. address.city The city associated with address.name. address.county The county associated with address.name. address.state The state in which address.name is located. address.country The country in which address.name is located. address.remakrs Any remarks associated with address.name, such as location, etc. address.building The building number associated with address.name. address.block The block in which address.name is located. address.floor The floor on which address.name is located. address.room The room in which address.name is located. address.postOfficeBox The PO Box number associated with address.name. contact.firstName The first name of the project contact. contact.lastName The last name of the project contact. contact.title The title of the contact (example: Dr., Mr., Mrs.) contact.positionName The position of the contact (example: manager). contact.profession Required. The profession of the contact. contact.emailAdress* Required. The email address of the contact. contact.mobilePhone The mobile phone number of the contact. contact.officePhone The office phone number of the contact. contact.otherPhone An additional or unspecified phone number of the contact. contact.pager The pager number of the contact. contact.fax The fax number of the contact. contact.skype The skype ID of the contact. contact.gender The gender of the contact. contact.remarks Internal remarks associated with the contact (example: do not disturb before 9 AM). project.id If applicable, the ID of the project with which the activity is associated. phase.id If applicable, the ID of the project phase with which the activity is associated. People - Skills Assignment When the People - Skills Assignment template is downloaded, all skills assignments, start dates and end dates will be populated in the selected format. This template can be used to manage skills assignments for employees in batch fashion. For example, a skill's assigned status could be changed for multiple employees to TRUE and then uploaded using the data loader instead of being changed in each person record in the Master Data Management application. Field Description id* Required. The unique ID of the technician. Name The name of the technician. Skill.{skillName}.assigned True or false (empty). Default is false. True when the skill is assigned to the technician. Skill.{skillName}.startDate If applicable, the start date of the skills assignment. This is commonly used for visas, time-based certifications, etc. Skill.{skillName}.endDate If applicable, the end date of the skills assignment. This is commonly used for visas, time-based certifications, etc. Data Loader Workflow 1. Download Template The first step is to download one of the data object templates. Templates are available in CSV and XLSX format, and users can select multiple data object templates to be combined into a single spreadsheet. 2. Format/Enter Template Data Next, you will enter or transfer information into the template and format it to align with the column naming and comma-delimiting rules. Data must be encoded in UTF-8. 3. Merge or Overwrite Next, you will select whether you want to merge the data contained in the template with records that may already exist in the database, or overwrite them completely. 4. Upload Template Data After selecting between Merge and Overwrite, you can then upload the data. Data can be uploaded in XSLX or CSV format. 5. Review Data The application will then review the template file for errors. When the data has successfully passed validation and been uploaded, it can then be reviewed in the relevant data object tab (example: Business Partner) of the Master Data Management Module. 1. Download Data Object Template In order to use the Data Loader, you must first download a data object template. View Details Select Template Format Explanation From the dropdown menu, you can select the data object template you would like to download. These templates are available in XLS, XLSX, and CSV format. Select Multiple Data Objects Explanation If necessary, you can also select additional data objects. The columns in the data object templates will then be combined into a single XLSX or CSV-formatted spreadsheet. For example, if you selected the Business Partner template in the first drodpown, and then the Address and Contact templates in the second dropdown, the templates would be aggregated into a single spreadsheet. 2. Format/Enter Template Data Next, you will enter data using the template, or format existing data to match the column naming conventions contained in the templates. Please take note of the following: Data Object templates are available in CSV, XLS, and XLSX format. Only UTF-8 encoding is currently supported. Only columns with an asterisk (*) are required. All other columns can be removed if not required for import. The following steps describe importing and exporting CSV to Excel. However, these steps can also be used to manage CSV-formatted tabular data from other sources for preparation in using the Data Loader. Note: It is recommended to remove all automatic formatting settings when editing XLS and XLSX templates in Microsoft Excel, as these settings can corrupt the data templates and result in errors when uploading. View Details Importing CSV to Excel Explanation After downloading a template, you could then import it to excel for data entry purposes by completing the following steps: Note: these steps are for Excel 2013 and later. Open Blank Workbook. Go to DATA tab. Click button From Text in the General External Data section. Select the CSV template you selected in the previous step. Follow the Text Import Wizard. (in step 2, select the comma delimiter for your text) Exporting to CSV After entering data or transferring existing data to align with the column-header naming conventions, you can then export the data to a CSV file by completing the following steps: Note: these steps are for Excel 2013 and later. Click the File tab and then select the Export option. From Export select the Change File Type option. In the "Other File Types" section, select the CSV (comma delimited) (*.csv) option. You will then be prompted to save the CSV-formatted file. 3. Merge vs Overwrite When uploading a data object file, you must first select the data object type you wish to overwrite or merge. View Details Option Description Merge By selecting this option, the information uploaded will be merged with any existing data object information that shares the externalId. Existing data will not be overwritten. Overwrite By selecting this option, all records that contain a matching identifier will be overwritten. Warning: If you are working with existing company data, this will result in missing or empty columns in the import file overwriting columns and fields with existing data in the company database. 4. Upload Template Data After you have completed entering data into the template, or formatting existing data to match the namining conventions and exported to CSV format, you can then upload the file. Note: When uploading XSLX or CSV-formatted data, the application will parse data based on columnar names, not data object template types. View Details Select the Object for which you would like to upload data. Select the CSV, XLSX, or XLS file from your computer. Select the Merge or Overwrite option (see above for more details). Click the Import Data button. 5. Review Template Data After you have successfully uploaded data, you can then review it from the tab specific to the data object file you have uploaded (example: business partner). View Details Appendix Data Object Table For more information on the Data Objects supported by the Data Loader, such as constraints, supported data types, and categories, refer to the following table. Data Object Table Model Versions Description ActivityCode 10, 11, 12 Provides information about activity code supporting activity code hierarchies. ActivityComposedCode 9, 10, 11 Provides composed code for an activity which is mainly used in case activity codes are organized in a structure of hierarchical form. Activity 13, 14, 15, 16, 17, 18 This is a common used object for different purposes, which has the special ability to have linked attachments (see Attachment). It is used for several cases like meetings, service task planning and appointments to store reminder, start and end date (see ActivityType.MEETING). After a meeting or engagement on customer side it is usually the case that there are some notes to be taken, so the next visitor has the full history about what is going on (see ActivityType.NOTE) In case of one had a call with a customer, there is the possibility to create an activity of an according type to make some notes that this phone call happened and what the content was (see ActivityType.CONVERSATION) Activities can be linked to objects (see object parameter) of different types like: Opportunities; ServiceCalls; SalesQuotation; SalesOrder; BusinessPartner. ActivityFeedback 9, 10, 11 Used to represent a feedback on the activity. ActivitySubType 11, 12, 13, 14 The object used to represent the available activity sub types available in the system. ActivityTemplate 8, 9, 10, 11 ActivityTopic 11, 12, 13, 14 The object used to represent the available activity topics available in the system. Address 15, 16, 17, 18 The address object is used to store all addresses which are available. Addresses consist of the known properties and are referenced to their parent object by the object reference. This way each address gets its standard parent object, but can be referenced by certain working objects like activities. In addition we take each address and enrich it with a related location object by asking Google for the corresponding coordinates. Alert 11, 12, 13, 14 Alerts serve as notifications about the most important information of the day or some system reminders which update every day. This object has a subject, some receivers to deliver the message to. Approval 10, 11, 12, 13 This object provides the ability to let users approve or decline requests assigned to them. As there are not all objects available on the devices there might exist approval cases we not even considered. We decided to give you a big remarks field, where one can put all the necessary decision information like order lines, discounts, etc. In addition there are predefined links for business partner and objectId/objectType referencing available which can be used to link to a document the user has permission for. For each assigned person, there exists a separate approval object - not like the alert where one alert has multiple receivers. Attachment 12, 13, 14, 15, 16 Attachment represents a binary file together with name, description and a reference to any other object. This object gets usually linked to activities where one can attach photos and audio notes or even pdf documents and other documents (depending on the client). This can be useful to transmit manuals or weekly detail reports to the field people. Attribute 10, 11, 12 Represents an attribute which can be defined on other domain objects. It's used in different modules of the solution, e.g. File Library, Service Suite generator, etc. AttributeValue 9, 10, 11 Represents a value of an Attribute. Batch 8, 9, 10 Batch number is a unique identifier of a batch which groups items (actually "item pieces") together. BatchQuantity 8, 9, 10, 11 Batch quantity represents a part of batch with defined number of items in this part. BlanketOrder 9, 10, 11 Blanket order represents a document that contains reserved items, i.e. items that are reserved for a business partner and will be delivered later in time. Branch 8, 9, 10, 11, 12 Represents a branch of a company. All Data Model objects can be assigned to zero or more branches. This might be useful for filtering results retrieved from the cloud, provided the permission system is configured accordingly. BusinessPartner 16, 17, 18, 19, 20 This object is a general representation of companies or customers. This is related to the basic system (e.g. SAP B1, SAP ECC, MS Dynamics CRM, ...). The businesspartner type indicates the kind of relationship to this company. For more information about types @see BusinessPartnerType. BusinessPartnerGroup 11, 12, 13, 14 BusinessPartnerGroups can be used to categorize business partners of a certain type. For this purpose, there is a code and name of the group along with an associated type. BusinessProcessStepDefinition 12, 13, 14, 15 BusinessProcessStepDefinitions are used in the resource planner to identify the steps necessary until a specific object (definitions made by DomainObjectModel) is finished. Category 13, 14, 15, 16 The object is used to categorize sales opportunities. Category can have a period of validity defined by the corresponding fields. CheckIn 8, 9, 10 Using Check-In the technician confirms that he made all steps/checks, which are necessary before he can start with the work on the equipment. ChecklistAssignment 10, 11, 12, 13 Link between business object and checklist template. ChecklistCategory 8, 9, 10 An object to manage checklist categories. ChecklistInstance 12, 13, 14, 15, 16, 17 This object represents an instance of a checklist instance. ChecklistInstanceElement 8, 9, 10 ChecklistTemplate 11, 12, 13, 14, 15, 16 This object represents a checklist template. Comment 8, 9, 10 The object used to represent comment which can be added to by user to other object types. CompanyInfo 12, 13, 14, 15 This objects properties are meant to represent the systems general information. CompanySettings 10, 11, 12, 13 An entity used to stored custom company settings. Settings are represented as strings and stored in a map. Competitor 10, 11, 12, 13 Represents a competitor involved in the process. CompetitorProduct 8, 9 Stores information about a competitor product found at a business partner that you collaborate with Configuration 8, 9 Configuration is yet another way of grouping persons to other objects. Contact 12, 13, 14, 15, 16 Contact represents related persons (e.g. employees) of a business partner. Country 9, 10, 11 Represents a country. County 8, 9 A county is a subdivision of a state. A country contains more states. A state contains more counties. Currency 9, 10, 11 Used to represent currency in monetary amounts. Defect 8, 9, 10 DocumentDiscount 8, 9, 10 Represents a document discount that is used during sales orders, quotations, etc creation. DocumentDraft 11, 12, 13 Draft of a sales order which is used as an intermediate document before sales order is finalized. EmployeeBranch 8, 9, 10 There should be such an object for all company branches where an employee can be assigned to, so one can see for which branch e specific person of type employee works. EmployeeDepartment 8, 9, 10 There should be such an object for all company department where an employee can be assigned to, so one can see for which department e specific person of type employee works. EmployeePosition 8, 9, 10 There should be such an object for all company positions where an employee is assigned to, so one can see in which position e specific person of type employee works. Enumeration 9, 10, 11 This class represents a collection of valid values for an EnumerationType. Equipment 14, 15, 16, 17, 18 Equipment is a specific item or machine installed on customer side with a certain address and serial number. The address of an equipment is indicated by a address object which points to the equipment. EquipmentSubType 8, 9, 10 Used to indicate all equipment sub types. ErpError 10, 11, 12, 13, 14 Represents error taken place in the ERP system. Expense 12, 13, 14, 15 This object represents expenses during travel like lunch, fuel, etc. Expenses are always assigned to a type which can be personal or per object or general. ExpenseType 11, 12, 13, 14, 15 This object specifies the available types for an expense. FieldConfiguration 8 Fields supported by Coresystems Cloud. File 8, 9, 10 Represent a meta information for actual file which is modeled with Attachment object. FileRef 8, 9, 10 Implements N:M relation between File Revision and object on which the File Revision is defined. FileRevision 8, 9, 10 Represents a revision of the given file. Filter 8, 9, 10 Filters are conditions which define a projection on the data read from the cloud. Typically filter contains a CQL expression which is evaluated over data in the cloud. GenericOrder 9, 10, 11 Generic order represents a document that may contain {@link GenericOrderItem}s of different types (e.g. ordered items, returned items, etc). Group 10, 11, 12, 13 Used to implement object grouping. Object is assigned to a group by keeping a group id in groups field. Groups can be organized in hierarchies by linking them via parent field. Incident 8, 9, 10, 11 Industry 10, 11, 12, 13 Industry is a business object that represents the industry which can be associated with a sales opportunity. InformationSource 10, 11, 12, 13 Source of information which led to the sales opportunity. Inventory 8, 9, 10 Represents an items inventory in a customer warehouse. Invoice 11, 12, 13, 14 Represents a invoice with all the necessary properties including net prices, gross prices and taxes. Invoices can only be created on business partners of type CUSTOMER and can only contain items with flag "salesItem" set to true. ItemCategory 11, 12, 13, 14 Represents a category which an item can be assigned to. For internal use only! Item 17, 18, 19, 20, 21 The item object represents the data of the item master data also called articles in some systems. ItemGroup 8, 9, 10 Indicates the available item groups of the system. These groups are used to make the selection by item group on all the devices. ItemPriceListAssignment 11, 12, 13, 14 Item pricelist assignments are used to make the link between an item and a pricelist by specifying a price and currency. Note: Multiple currency price lists are not supported! ItemReturnReason 9, 10, 11 Specifies the reason for an item return. ItemType 8, 9, 10 This indicates the available item types of the system. Item types are used to indicate the different purposes of an item. ItemWarehouseLevel 11, 12, 13, 14 This object represents the stock level of a specific item in a warehouse. LevelOfInterest 10, 11, 12, 13 Represent level of interest in the sales opportunity. LocationNumberSeries 8, 9, 10 The entity that keeps reference between locations, their series numbers and item types. Very specific for Dr. Schar. Material 14, 15, 16, 17, 18 This object is used while a field technician is working on a service call and needs some material from his car stock. After technician fixes an issue on customer side,he creates a material object for each item used. Mileage 12, 13, 14, 15, 16 This objects is meant to enter mileage for traveling to customer. MileageType 11, 12, 13, 14 This object specifies the available types for a mileage. ObjectGroup 11, 12, 13, 14 Object group represents a group of objects of a given type which then can be assigned to certain objects. ObjectRating 10, 11, 12, 13 This object represents a general rating of a service or something else. At the moment it is used to indicate the customers satisfaction for a completed service call. PaymentTerm 11, 12, 13, 14 This object represents the terms of payment supported by the combination of system and pricelist. This is used to identify the proper payment terms which are displayed while creating sales orders and other objects which have prices associated. PaymentType 12, 13, 14, 15 This object represents the types of payment supported by the system. Person 15, 16, 17, 18, 19 Person represents the employees, users or sales employees of a company. A physical person can have up to 3 different entries like: Person A, ERPUSER Person A, EMPLOYEE Person A, SALESEMPLOYEE --> these 3 entries are then linked together by using the property refID which indicates a physical person. For this object common sense properties are not specially documented. Special for this class is that OWN permission is filtered by the person's id. PersonReservation 13, 14, 15 Person reservation for a specific time and business partner. PersonReservationType 11, 12, 13, 14 Person reservation type which specifies what kind of reservation can be taken in resource planner. PriceList 11, 12, 13, 14 Pricelist object which is used to make prices available in items and stock module or during creation of sales documents and materials. Please note: Multiple currency price lists are not supported. ProductionOrder 10, 11, 12, 13 Represents a production order, with the information necessary to book TimeEfforts on it. PropertyMeta 8, 9, 10 Meta data for all available properties the system. This meta data contains a link to the objectType which this information belongs to and different other settings to let the system configure the behaviour on the clients. PurchaseOrder 11, 12 Represents a purchase order with all the necessary properties including net prices, gross prices and taxes. Purchase ordres can only be created on business partners of type SUPPLIER and can only contain items with flag "purchaseItem" set to true. Reason 10, 11, 12, 13 Represent a reason to go for a sales opportunity. ReportData 11, 12, 13, 14 Object which represents a report. ReportTemplate 10, 11, 12, 13, 14, 15 Report template object used to define structure and layout for report generation. Requirement 8 ReservedMaterial 11, 12, 13, 14 This object is used while some materials are reserved for e.g. a Service Call. New connector sends ReservedMaterial for serial number managed and batched managed items differently: serial number managed items - 1 ReservedMaterial object per serial number batch managed items - 1 ReservedMaterial object per batch quantity item is managed by serial number AND batch - 1 ReservedMaterial object per batch quantity item is NOT managed by serial number or batch - 1 ReservedMaterial object with reserved quantity and no links to serial number or batch SalesOpportunity 12, 13, 14, 15 SalesOpportunity is a business object that represents the sales opportunity data. Sales Opportunity include potential sale volumes that may arise from business with customers and interested parties. SalesOrder 13, 14, 15, 16, 17 Represents a sales order with all the necessary properties, including net prices, gross prices and taxes. SalesOrders can only be created on business partners of type CUSTOMER or LEAD and can only contain items with flag "salesItem" set to true. SalesQuotation 12, 13, 14, 15, 16 Represents a quotation with all the necessary properties including net prices, gross prices and taxes. SalesQuotation cannot be created on business partners of type SUPPLIER, CUSTOMER or LEAD and can only contain items with flag "salesItem" set to true. SalesStage 10, 11, 12, 13 The SalesStage object enables to define sales stage and their probability percentage. For example: Lead, Meeting, Quotation, Negotiation, and Order. These definitions are used as default values for the SalesOpportunity object. ScreenConfiguration 8, 9, 10, 11 Class for storing screen configuration. Sequence 8, 9, 10 Sequence are used to automatically generate values for various object fields. SerialNumber 8, 9, 10 Serial numbers is a unique number that identify an item. Example if quantity is 2, one need to indicate serial numbers of the two items. ServiceAssignment 20, 21, 22, 23, 24 ServiceAssignment object which allows special assignments of person to a servicecall. This object is available for ressource planner only. ServiceAssignmentStatusDefinition 9, 10, 11, 12, 13 Defines the meaning of the service assignment status. ServiceAssignmentStatus 8, 9, 10, 11, 12, 13 Represents status of service assignment. ServiceCall 14, 15, 16, 17, 18, 19, 20, 21 Service call or ticket which indicates a request from customer to a certain problem or service. ServiceCallOrigin 11, 12, 13, 14 Used to specify all available origins for a service call. ServiceCallProblemType 11, 12, 13, 14 Used to specify all service call problem types available. ServiceCallStatus 11, 12, 13, 14 Used to specify all service call status available in the system. ServiceCallType 11, 12, 13, 14 Used to indicate all available service call types in the system. ServiceCheckout 10, 11, 12, 13 ServiceCheckout object which allows special user to checkout the services done at customer side. ServiceContract 8, 9, 10 Contracts are agreements between the Customer and Vendor to supply materials/services for a specific price between a fixed period of time. ServiceContractEquipment 9, 10 This object represents the relation between service call and equipment. ServiceErrorCode 8, 9, 10 Final Error Code that the Technician can generate ServiceErrorCodeItem 9, 10, 11 Hierarchical construct which lets one build an error code by predefined ServiceErrorCodeItem structure. Used during ServiceCheckout process. ServiceSuiteConfig 9, 10, 11 Represents configuration defined for Service Suite and used in Task Configurator for object generatioin. ShippingType 11, 12, 13, 14 Represents all shipping types available in the system. E.g. a shipping type is used during the creation of a sales order. There the user is prompted to choose one of those. Signature 10, 11, 12, 13 Used for any type of signature taken on the mobile device and processed in the system or vice versa. Skill 8 State 8, 9 A state is a subdivision of a country. A country contains more states. A state contains more counties. StockTransfer 9, 10, 11, 12 Stock transfer represents a item move from one warehouse to another. SyncObjectChangelog 9 SyncObject 5, 6, 7, 8, 9, 10 Tag 8 Tax 8, 9 TimeEffort 11, 12, 13, 14, 15 This object represents efforts one does for a specific customer. In usual cases efforts can be charged to the customer and bring money to the company doing the services. TimeEfforts can be booked on business partners, sales orders, sales quotations, opportunities, production orders, service calls and time projects. TimeProject 11, 12, 13, 14 Time projects are thought as a small container for internal projects or similar objects which allow to book time on but are not really related with another business object. TimeSubTask 11, 12, 13, 14 Represents a sub time task. This object is for internal use only. TimeTask 13, 14, 15, 16, 17 TimeTasks specify the work one has done on customer side like a work process, type of service, or some specific ways of this. Translation 8, 9 Central place for storing everything what can be translated. TransportCost 10, 11, 12 Specifies transport costs for items delivery. UdfMeta 10, 12, 13, 14 Meta data for all available udf values in the system. This meta data contains a link to the objectType which this information belongs to and different other settings to let the system configure the behaviour on the clients. UdfMetaGroup 8, 9, 10 Usage 11, 12, 13, 14 This specifies the usage of sales documents lines. UserSettings 10, 11, 12, 13 An entity used to stored custom user settings. Settings are represented as strings and stored in a map. UserSyncConfirmation 12 Internal use only!!! VisitorReport 9, 10 Represent a report created after visiting a customer site. The object heavily exploit UDFs for transferring information. Warehouse 12, 13, 14, 15 Warehouse object from which a technician can take its material or which is considered to indicate if an item is on stock or not. WorkTime 10, 11, 12, 13, 14 Work times are used to let the user enter the time he worked overall, not related to any services or customer support he did - it is just the come and leave statement including a break. WorkTimeTask 11, 12, 13, 14 This is used to represent the available work time tasks or types available in the system like vacation, holiday, military service, etc. Plugin 8 A plugin can be any JS UI widget. Project 8 Used to reprsent a project. Project Phase 8 Used to represent a project phase or subphase. Now Plugin 8 A plugin for the Now portal. This plugin can be any JS UI widget. Now Plugin Instance 8 Now Plugin Instance Set 8, 9 Now Short URL 8 Person Work Time Pattern 8 A work time pattern associated with a person. Work Time Pattern 8 A work time pattern. Error Codes When uploading the csv-formatted files with object data, the application may return error code messages. Refer to the following table for more details on error code messages. Error Codes Error Code HTTP Response Code Default message CA-01 A cql syntax error discovered around position [{0}] : [{1}]. 400 CA-02 Expand string [{0}] does not match the expand pattern. 400 CA-03 Field [{0}] of resource [{1}] cannot be expanded. 400 CA-04 Can not find DTO field name [{0}] in resource [{1}]. 400 CA-05 The complex field [{0}] of resource [{1}] does not specify any of embedded fields. 400 CA-06 DTO field name [{0}] of resource [{1}] does not match the DTO field name pattern. 400 CA-07 Can not generate sequence value for [{0}] field [{1}]. 400 CA-08 Uploaded object has value [{0}] which is either 'null' or in range of automatically generated values. 400 CA-09 Could not deserialize uploaded object to [{0}], because [{1}] 400 CA-10 Object [{0}, {1}] is not valid. 400 CA-11 OrderBy [{0}] does not match the orderBy pattern. 400 CA-12 Pagination values should be greater then zero, page [{0}] pageSize [{1}]. 400 CA-13 Permission denied for uploading resource [{0}, {1}] 403 CA-14 Resource [{0}] does not match the resource name pattern. 404 CA-15 Can't find class for resource [{0}]. 404 CA-16 Shaping [{0}] does not match the shaping pattern. 400 CA-17 Invalid DTO. Name [{0}], version [{1}]. 400 CA-18 DTO name [{0}] does not match the DTO name pattern. 400 CA-19 No resource found for [{0}] version [{1}]. 400 CA-20 No DTO version specified for resource [{0}]. 400 CA-21 Invalid ETO [{0}]. 400 CA-22 Resource [{0}] doesn't support ETO version [{1}]. 400 CA-23 The URL query string contains not supported parameters {0}. Allowed query string parameters are {1}. 400 CA-24 Can not create value [{0}] of type [{1}]. 400 CA-25 Permission denied for refreshing [{0}] resource with id [{1}]. 403 CA-26 Resource [{0}] with id [{1}] is not found. 404 CA-27 Resource concurrent modification detected. Last changed [{0}] of resource [{1}, {2}]. 409 CA-28 Resource [{0}] with id [{1}] is blocked. 423 CA-29 Report template with id [{0}] not found. 400 CA-30 Embedded report template with name [{0}] not found. 400 CA-31 Error while building the report [{0}]: [{1}]. 400 CA-32 Error while compiling one of the report files [{0}]. 400 CA-33 Error while coping one of the report files [{0}]. 400 CA-34 No attachment found for report template with id [{0}]. 400 CA-35 More than one attachment found for report template with id [{0}]. 400 CA-36 Parameter(s) {0} used in query [{1}] must be set. 400 CA-37 Report template field can't be empty. 400 CA-38 Report bundle must not contain any directories [{0}]. 400 CA-39 Report bundle is missing [{0}] file. 400 CA-40 The [{0}] with id [{1}] can't be deleted because it is referenced by {1}. 422 CA-41 Can not create resource [{0}, {1}] as it already exists. 422 CA-42 Retrieved resources can not be organized in a single root hierarchy. Resources {0}. 422 CA-43 Activity template resource [{0}] should have exactly one group defined. Actual number of groups [{1}] 422 CA-44 Sequence for [{0}#{1}] is not defined 422 CA-45 Real hierarchy definition for [{0}] is not valid as resource [{1}] has status [{2}]. Can't generate service suite. 422 CA-46 Resources of type [{0}] with ids {1} are not found. 422 CA-47 Resource [{0}] with id [{1}] is not is state [{2}]. Can't remove draft resources. 422 CA-48 Generic hierarchy definition for [{0}] is not valid as resource [{1}] has status [{2}]. Can't generate service suite. 422 CA-49 Permission denied for deleting [{0}] resource with id [{1}]. 403 CA-50 Permission denied for copying [{0}] resource with id [{1}]. 403 CA-51 Configuration level equipment [{0}] defined for configuration does not have status [{1}]. 422 CA-52 Permission denied for generating service suite for [{0}]. Expected permission [{1}]:[{2}] for [{3}] is not granted. 403 CA-53 Permission denied for deleting service suite for [{0}]. Expected permission [{1}]:[{2}] for [{3}] is not granted. 403 CA-54 Can not create value [{0}] of type [{1}]. 422 CA-55 Equipment for configuration [{0}] is not defined. 422 CA-56 Can not parse condition [{0}] for activity template [{1}]. Cause [{2}]. 422 CA-57 No equipment is defined for activity template [{0}]. 422 CA-58 Next sequence value for [{0}#{1}] can't be generated. Check sequence settings (e.g. activated, max value, etc). 422 CA-59 No resources of type [{0}] with field [{1}] equal to [{2}] found. 422 CA-60 More than one resource of type [{0}] with field [{1}] equal to [{2}] found. 422 CA-61 Service call for configuration [{0}] is not defined. 422 CA-62 Can not change service suite configuration [{0}] status to [{1}] as there are no generated resources found for the it. 422 CA-63 No service suite configurations found for service call [{0}]. 422 CA-64 There are [{0}] service suite configurations found which are not in status [{1}]. 422 CA-65 Company setting [{0}] is not defined. 422 CA-66 Permission denied for releasing service call suite for [{0}]. Expected permission [{1}]:[{2}] for [{3}] is not granted. 403 CA-68 More than one attachment exist for category [{0}] and source object [{0}]. 422 CA-69 Can not open file because of its invalid format. File [{0}]. 422 CA-70 The xls attachment should contain at least one sheet. Actual sheet number [{0}]. File [{1}]. 422 CA-71 The first xls sheet should contain at least one column. Actual number of columns [{0}]. File [{1}] 422 CA-72 No attribute or field names are defined. File [{0}]. 422 CA-73 No attributes defined in header cells {0}. File [{1}]. 422 CA-74 Exactly one attribute for each of {0} names should exist. File [{1}]. 422 CA-75 XLS file has no content. File [{0}]. 422 CA-76 Can not modify service suite configuration [{0}] and related objects as it is in status [{1}]. 422 CA-77 All cells of the excel file should be of string type. File [{0}]. 422 CA-78 Some errors have been encountered during excel validation. File [{0}]. 422 CA-79 Row [{0}] has invalid size [{1}]. Row should have as many values as attributes defined [{2}]. 422 CA-80 Row [{0}] has at least one cell with no value in it. 422 CA-81 Row [{0}] should have exactly one activity template associated. Actual number of activity templates [{1}]. 422 CA-82 Some attributes are defined multiple times. Check excel column headers. File [{0}]. 422 CA-83 Row [{0}] has values which are already present in the same file earlier. 422 CA-84 The [{0}] from [{1}] has value in wrong format. The correct format is [{2}]. 422 CA-85 Company setting [{0}] should have a value higher than [{1}]. 422 CA-86 There already exists a file revision with language [{0}] and revision [{1}] for file [{2}]. 422 CA-87 No objects have been generated because no attribute values are defined on service suite configuration [{0}]. 422 CA-88 No objects have been generated because no activity templates were found for service suite configuration [{0}]. 422 CA-89 Attribute [{0}] should have the same object type as its parent [{1}]. 422 CA-90 Function [{0}] can't be used on field [{1}] due to unsupported data type. 400 CA-91 Resource [{0}] can't be copied as there is no predefined copier for resource type [{1}]. 422 CA-92 Generic hierarchy definition for [{0}] is not valid. Looks like there are loops in the hierarchy. Number of source elements [{1}], number of elements in the built hierarchy trees [{2}]. Can't generate service suite. 422 CA-93 Some filed names are defined multiple times. Check excel columns definition. File [{0}]. 422 CA-94 No field names defined in columns {0}. File [{1}]. 422 CA-95 No fields found {0}. File [{1}]. 422 CA-96 No column categories defined {0}. Check excel columns definition. File [{1}]. 422 CA-97 Following column categories {0} are invalid. Allowed categories are {1}. File [{2}]. 422 CA-98 Column category order {0} is invalid. File [{1}]. 422 CA-99 Object [{0}:{1}] not found. 404 CA-100 UdfMeta with name [{0}] not found. 404 CA-101 Object [{0}] not found. 404 CA-102 Parameter "to" should have value grater than "from" parameter 400 CA-103 Entity to delete has at least one relation of type [{0}] 422 CA-104 Parameter(s) [{0}] are missing 400 CA-105 Can not create relation object. Object with the same relations already exists: [{0}:{1}] and [{2}:{3}]. 422 CA-106 Can not update relation object. Object with the same relations already exists: [{0}:{1}] and [{2}:{3}]. 422 CA-107 Aggregate function string [{0}] does not match the aggregate function pattern. Please use one of those functions COUNT, MIN, MAX, SUM or AVG. Example: count(ServiceCall.id)@countingResultAlias 400 CA-108 GroupBy string [{0}] does not match the GROUP BY function pattern. A valid GROUP BY can look for example: BusinessPartner.currency 400 CA-109 Multiple occurrence of the same alias [{0}] for different aggregate functions 400 CA-110 Referenced resource can't be inferred for resource [{0}] field [{1}]. 422 CA-111 Can not delete enumeration value [{0}] as it is used by at least one resource of type [{1}]. 422 CA-112 Invalid Json [{0}] 400 CA-113 Query syntax error at position [{0}] for [{1}]. Please inspect the token [{2}]. 400 CA-114 The parameter [{0}] is missing. 400 CA-115 The query parameter [{0}] is empty. 400 CA-116 You can not use the complex field [{0}] into expression evaluation. 400 CA-117 Missing declaration into FROM or JOINs clauses for resource [{0}]. 400 CA-118 There is no such field [{0}]. Please consider that fields names are case sensitive. 400 CA-119 Query syntax error at position [{0}] for [{1}]. Please consider [{2}] 400 CA-120 Undefined token [{0}]. 400 CA-121 Can not perform [{0}]: [{1}], for the arguments of types [{2}]. Please consider to change the query portion: [{3}] 400 CA-122 Unknown type for field [{0}] . 400 CA-123 Unsupported operation(or function) [{0}]. This operation can not be translated into SQL syntax. 400 CA-124 Unsupported operation or function: [{1}]. 400 CA-125 Invalid parameters number for function: [{0}]. This function allows [{1}] parameters. Please consider to change the query portion: [{2}] 400 CA-126 The [{0}] clause requires a [{1}] expression. 400 CA-127 Can not perform operation: [{0}]. Please consider to change the query portion: [{1}] 400 CA-128 Can not perform function: [{0}]. Please consider to change the query portion: [{1}] 400 CA-129 Only one configuration can be marked as default. 400 CA-130 Object [{1}, {2}] is not valid. Name [{0}] is not unique. 400 CA-131 One or more [Person] objects are already assigned to a different configuration. 400 CA-132 One or more [ScreenConfiguration] objects are already assigned to a different configuration. 400 CA-133 The query parameter [{0}] has a wrong value. Please use: [{1}] 400 CA-134 A Structural output format, can be used when you have only one resource definition into the From clause & you are using a single Join clause (of type JOIN or LEFT OUTER JOIN). 400 CA-135 Can not perform query, because of a database error. Error code: [{0}] 400 CA-136 Please use a positive natural number for representing a timestamp. Please consider to change the query portion: [{0}]. 400 CA-137 Invalid reference identifier format. Please consider to change the query portion: [{0}]. 400 CA-138 Can not perform query. Only one join is allowed when using a RIGHT OUTER JOIN or a FULL OUTER JOIN 400 CA-139 Can not perform query. When using Joins, you can have only one resource defined into From clause. 400 CA-140 Please use the date & time format pattern: [{0}]. Please consider to change the query portion: [{1}]. 400 CA-141 Resource identifier [{0}] is not equal to the sync object identifier [{1}]. 400 CA-142 The UDF having [{0}] does not exist for resource [{1}]. 400 CA-143 Invalid parameters number for operation: [{0}]. This operation allows [{1}] parameters. Please consider to change the query portion: [{2}] 400 CA-144 Can not generate a code value for [{0}]. 400 CA-145 There is no support for the UDF type [{1}]. You can use this UDF as a text value by using the optional parameter 'useUdfAs' with values: 'allAsText' or 'unknownAsText' 400 CA-146 You are trying to reference an object by externalId using a DTO version that does not support externalId. Please use a DTO version that extends SyncObjectDTO_V9 or above. 422 CA-147 You are not allowed to update the resource identifier. 422 CA-148 Please use the time format pattern: [{0}]. Please consider to change the query portion: [{1}]. 400 CA-149 You can not use the same resource name declaration [{0}] for multiple times. Please correct the WHERE (or JOINs) resources declarations. 400 CA-150 Pagination is supported only for [{0}] output format 400 CA-151 Invalid query parameter [{0}]. Reason: [{1}]. 400 CA-152 There is no Udf [{0}] into UdfMeta associated to the resource [{1}]. 400 CA-153 You can not use NULL keyword into the query. If you want to check for null, please use IS NULL or IS NOT NULL syntax. 400 CA-154 Object [{0}] with externalId [{1}] was not found. 422 CA-155 Cannot parse HTTP request. 400 CA-156 There are too many requests in the batch. Maximum is set to [{0}]. 422 CA-157 Because the server is busy at this moment, your query was cancelled. Please try again later. 400 CA-158 The query was cancelled because it takes more then 30 seconds to execute. 408 CA-159 Please do not mix explicit & implicit joins. Try to rethink the query by using only explicit joins. 400 CA-160 When using FULL OUTER JOIN or RIGHT OUTER JOINS, the joining condition must be merge-joinable or hash-joinable. Try to rethink the query. 400 CA-161 Fail to read the file. 400 CA-162 Internal error. Please contact support. 400 CA-163 One or more columns names are empty. 400 CA-164 The resource name [{0}] in the URL path is not valid. 400 CA-165 Please upload a file. 400 CA-166 The file does not exist 400 CA-167 Please use an alias for the expression [{0}]. Example: SELECT count(bp.id) AS 'countResult' FROM BusinessPartner bp 400 CA-168 You can not use the same alias [{0}] for more then one expression. 400 CA-169 Please don't use an alias for the expression or field [{0}]. 400 CA-170 When using aggregate functions, the GROUP BY clause should contain the same fields as the SELECT clause. 400 CA-171 You can not use pagination in combination with aggregate functions 400 CA-172 You can use pagination in combination with OFFSET or LIMIT sql clauses. 400 CA-173 For using pagination, you have to use both [{0}] and [{1}] parameters 400 CA-174 You can not use aggregate functions (or aggregate functions aliases) into [{0}] clause. 400 CA-175 The import file should be less then [{0}] megabytes. 400 CA-176 The import file should contain less then [{0}] rows of data. 400 CA-177 There is not such type [{0}] for udf meta fields. The allowed types are [{1}]. 400 CA-178 There is already a udf meta named [{0}] having a different type then [{1}]. 400 CA-179 For updating an object of type [{0}] you need: READ and also CREATE or UPDATE permissions. 400 CA-180 The import file does not contains the following required columns: [{0}]. 400 CA-181 The value [{0}] is not valid for the expected [{1}] udf type 400 CA-182 There is already an UdfMeta having the name [{0}], but with a different udfType then [{1}] 400 CA-183 We detect a problem for column [{0}]. [{1}] 400 CA-184 The number of columns into this row is different from the number of column headers. 400 CA-185 Identification column [{0}] can not be empty. 400 CA-186 Unrecognized column names [{0}] for object [{1}]. Please use the column names provided in the template or create new properties by using the User Defined Fields standard: UDF.columnName[dataType] (eg: UDF.price[int]) 400 CA-187 Status transition for approval is invalid. Approval can not change from status [{0}] to [{1}] 422 CA-188 Status transition for object is invalid. Object can not change from status [{0}] to [{1}] 422 CA-189 Invalid custom rule [{0}] 400 CA-190 Invalid type [{0}]. Available types are {1} 400 CA-191 Permission denied for search in documents of type [{0}]. Read all permissions are missing for the following domain objects {1}. 403 CA-192 No valid subscriptions 403 CA-193 Only query for id is allowed for ProfileObject 400 CA-194 Object with specified external id is not found. But object with specified id already exists 422 CA-195 Overlap with exclusive reservation is not allowed. Resource [{0}]. 422 CA-196 Changing enumeration type is not allowed 400 CA-197 Cannot process attachment of id [{0}] 422 CA-198 Maximum attachment [{0}] size exceeded. 422 CA-199 Person of type [{0}] and user name [{1}] already exists with different id! 422 CA-200 Object [{0}, {1}] already exists but with different id! 422 CA-201 Object [{0}, {1}] doesn't have a unique externalId [{2}] 422 CA-202 Object [{0}, {1}] doesn't have a unique code [{2}]. 422 CA-203 Object [{0}, {1}] contains invalid object refence. 422 CA-204 Assignment [{0}] cannot be created on a closed service call. 422 CA-205 Wrong file extension [{0}] allowed extensions are [{1}]. 422 CA-206 Excel file does not contain sheet named as resource [{0}]. 422 CA-207 Report template with name [{0}] is an offline report and can't be build in the Cloud. 400 CA-208 User is not assigned to any Person object. 403 CA-209 Element [{3}] in collection [{2}] in object [{0}:{1}] not found. 400 CA-210 [{0}] not specified, BAD_REQUEST) 400 CA-211 Validation fails. Reasons: [{0}] 422 CA-212 Activity [{0}] can not be cancelled. Not in stages [DISPATCHING, EXECUTION] 422 CA-214 Wrong file extension [{0}] allowed extensions are [{1}]. 422 CA-215 Wrong resource [{0}]. 422 CA-216 Wrong additional resource [{0}]. 422 CA-217 Unsupported resource [{0}]. 422 CA-218 Wrong additional resource [{0}] for resource [{1}]. 422 CA-219 Found more than one object by field [{0}]. 422 CA-220 Field [{0}] on object [{1}] must have not empty value. 422 CA-221 Field [{0}] on object [{1}] has invalid value. Valid values are [{2}]. 422 CA-222 Manager [{0}] for this person [{1}] is invalid. Manager must be of type EMPLOYEE and ACTIVE. 422 CA-223 There is another data indexing process started for the given company. Process started on [{0}]. 422 CA-224 There was an error in custom rule [{0}]. 500 CA-225 Current user is not the issuer of the approval. Cannot cancel approval [{0}]. 422 CA-226 Activity [{0}] of Approval [{1}] does not have ServiceAssignment. 422 CA-227 State [{0}] of approval [{1}] is not PENDING or REVIEW. 422 CA-228 Current user [{0}] is not the issuer of the approval [{1}]. 422 CA-229 Approvals [{0}] not found. 422 CA-230 Current user [{0}] cannot modify approval [{1}]. 422 CA-231 Activity not found for approval [{0}]. 422 CA-232 Type [{0}] of approval [{1}] is not related to activity. 422 CA-233 Entity [{0}] is not allowed to search. 400 CA-234 Join chain has not connected elements [{0}]. 400 CA-235 [{0}] allowed only for standalone companies. 400 CA-236 UDF data type required for header [{0}] 400 CA-237 Join in query options is not properly formed. 400 CA-238 Constraint violation [{0}]. 400 CA-239 [{0}] with id [{1}] not found. 400 CA-240 {0}. 400 CA-241 Equipments [{0}] and [{1}] have reference to each other in the hierarchy. 422 CA-242 No identifiers provided to resolve branches in equipment hierarchy. 400 CA-243 Resources of type [{0}] with ids {1} are not found. 400 CA-244 Client is not allowed for this user. 403 CA-262 End date cannot be before start date. Bad request. 400