8 Data Model

Source: This article refers to 8 Data Model
Note: Coresystems uses OAuth 2.0 for authorization. For more information on OAuth 2.0, including information, refer to the following topic.

The domain model is a composite of the current Data Transfer Objects (DTOs).

DTO versions are snapshots in time of our domain model. Each time we change/add/remove properties to resources in our domain, we create a new DTO version for the modified resource. This is done to ensure that, when changing the domain model, we can maintain backwards compatibility for old DTO versions.

Since our API supports “expand” queries, clients can choose exactly what they want to get from the cloud. Please note that Resource/Field names used in the url are case sensitive. The convention is to use camel case naming with uppercase first letter for resources (e.g. ServiceCall) and lowercase first letter for fields (e.g. createPerson).

For guidance on how to map our domain model to yours, please visit the Mapping Guidelines below.


8.1 Data Transfer 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.
CustomRule 8, 9 The rules binds an event, conditions and an action.
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.

8.1.1 Entity Class Diagram

This diagram describes the concepts used within Coresystems applications from a Business perspective. There is no 1:1 relationship between the entities defined here and the physical objects that exist in the cloud database.


8.2 Mapping Guidelines

One of the most critical questions that arise during integration is: How can I map my model to your model?

To answer this question, you should follow the guidelines below:

  • Use an Excel file. Try to find matching between resources in the two models. You can use an Excel file having two columns: Our model and Your model. Try to find similarities.
  • User Defined Fields (or UDFs). It is impossible for our model to acheive a perfect, one-to-one relationship with your model. There are situations when a resource in your model will contain properties that do not correspond to our domain model. For such cases we provide the User Defined Fields functionality.
  • No restriction when linking resources (ObjectRef type). There are resources that have some special properties of type ObjectRef (eg. Address.object). You can use those properties to create references to any other resource type (For more details, please read about the objectref type).

8.3 User Defined Fields (UDFs)

UDFs are virtual properties of a resource. By “virtual”, we mean that you can add or remove a property to a resource at any time.

Let’s take an example. Suppose that in your model, you have a business partner resource. Your business partner has a SWA_CT_PrjCode property.
You are interested in finding a correspondent property for SWA_CT_PrjCode in our domain model. However, in our domain model, there is no such property.

The only option you have is to create a UDF for this SWA_CT_PrjCode property.

Creating a UDF involves two steps:

  • First, we create the UDF description: the default value, property type, property owner, external ID etc. We store such information about an UDF into a UdfMeta resource.

Below, we show an example of a UdfMeta for a String property that can be assigned to a business partner resource (“objectType”: “BUSINESSPARTNER”). The name of the property is called SWA_CT_PrjCode.

Create UDF


Request


POST: https://{dataCloudURL}/api/data/v4/UdfMeta?account=scribe&company=Ambit%20AG&clientIdentifier=COR_CON_NONE&dtos=UdfMeta.14



Request Body


{ "description": "Project Code", "type": "STRING", "objectType": "BUSINESSPARTNER", "name": "SWA_CT_PrjCode", "valueLength": 10, "externalId": "Custom_ID_12345" }



Response


{ "data": [ { "udfMeta": { "description": "Project Code", "type": "STRING", "objectType": "BUSINESSPARTNER", "inactive": false, "id": "61599E3B4BBA4F2DAF83BE08B6DD9DB9", "lastChanged": 1459254725925, "createPerson": "3080357EE48A48CBA233CFE86BB99237", "externalId": "Custom_ID_12345", "createDateTime": "2016-03-29T15:32:05+03:00", "name": "SWA_CT_PrjCode", "valueLength": 10, "lastChangedBy": "3080357EE48A48CBA233CFE86BB99237", "syncStatus": "BLOCKED" } } ] }



Second, for a Business Partner we will set a value for this new UDF. Below we use the PATCH functionality. We refer to this UDF by using its external ID

Set UDF Value


Request


PATCH https://{dataCloudURL}/api/data/v4/BusinessPartner/12A14047F88F4F71A679FA59612AD1B0?&account=scribe&company=Ambit%20AG&clientIdentifier=COR_CON_NONE&dtos=BusinessPartner.20



Request Body


{ "udfValues":[ { "meta":{ "externalId":"Custom_ID_12345" }, "value":"MyProjectCode" } ] }



Response


{ "data": [ { "businessPartner": { "country": "CH", "code": "L10002", "city": "Horgen", "language": "DE", "id": "12A14047F88F4F71A679FA59612AD1B0", "udfValues": [ { "meta": "61599E3B4BBA4F2DAF83BE08B6DD9DB9", "value": "MyProjectCode" } ], "lastChangedBy": "3080357EE48A48CBA233CFE86BB99237", "paymentTerm": "B77AC875CA6A4D65B0296482BB0E3BCC", } } ] }



The UDFs values are returned into a list named: “udfValues”. For each UDF, we return a pair of (meta, value) information. The “meta” represents the identifier of the UdfMeta associated with this UDF.

As you can see, the business partner is already updated with the new UDF value.

For learning how to use UDFs in querying, please visit the querying page.


8.4 Using Enumerations

One of the data type we support is string. A property of type string can have constraints: limited length or limited set of valid values.

We use enumerations to restrict the values of a string property to a limited set of valid values.

Let’s take an example. In our domain model we have the business partner resource. One of its properties is named type. This type is then defined as follows:

/\\*\\*
	 \\* Type of business partner (e.g. LEADER, SUPPLIER,...)
	 \\*/
	@Enumeration(EnumerationType.BUSINESSPARTNER_TYPE)
	private String type;

You can see that the type property is annotated with this Enumeration annotation, having the value EnumerationType.BUSINESSPARTNER_TYPE (remember this value).

What does this mean? This means we allow a limited set of valid values for this type property.

Where are whose valid values defined? The allowed values comes from Enumeration resources, having the the property enumType value equals to BUSINESSPARTNER_TYPE.

When your company is created, we automatically generate some default enumeration resources. You can change or add new enumerations, by using our APIs that allows data modification.

Suppose you want to get all the valid values of the business’s type property. We will have to build a query for this.


Request


POST https://{dataCloudURL}/api/query/v1?account=scribe&company=Ambit%20AG&clientIdentifier=COR_CON_NONE&dtos=Enumeration.11



Request Body


{"query":"SELECT e FROM Enumeration e WHERE e.enumType='BUSINESSPARTNER_TYPE'"}



Response


{ "data": [ { "e": { "code": "LEAD", "enumType": "BUSINESSPARTNER_TYPE", "createDateTime": "2012-12-28T12:03:22+02:00", "name": "LEAD", "position": 2, "id": "C61DEA20077A4501B07B432E023800C5", "nameTranslations": { "CS": "Potenciální klient", "DE": "Interessent", "JA": "リード", "EN": "Lead", "IT": "Cliente potenziale", "FR": "Piste", "HU": "Potenciális ügyfél", "ES": "Cliente potencial", "NL": "Lead" } } }, { "e": { "code": "CUSTOMER", "lastChanged": 1356689001721, "enumType": "BUSINESSPARTNER_TYPE", "createDateTime": "2012-12-28T12:03:21+02:00", "name": "CUSTOMER", "position": 0, "id": "923861914B594086B9CBA881C7D2FA25", "nameTranslations": { "CS": "Zákazník", "DE": "Kunde", "PT-BR": "Cliente", "JA": "得意先", "EN": "Customer", "IT": "Cliente", "PL": "Klient", "FR": "Client", "HU": "Ügyfél", "ES": "Cliente", "NL": "Klant", "ZH-CN": "客户" } } }, { "e": { "code": "SUPPLIER", "lastChanged": 1356689002023, "enumType": "BUSINESSPARTNER_TYPE", "createDateTime": "2012-12-28T12:03:22+02:00", "name": "SUPPLIER", "position": 1, "id": "07D3CCD031DF4029970F3DA80E360BAB", "nameTranslations": { "CS": "Dodavatel", "DE": "Lieferant", "PT-BR": "Fornecedor", "JA": "仕入れ先", "EN": "Supplier", "IT": "Fornitore", "PL": "Dostawca", "FR": "Fournisseur", "HU": "Beszállító", "ES": "Proveedor", "NL": "Leverancier", "ZH-CN": "供应商" } } } ] }



We got three enumerations resources having the enumType = BUSINESSPARTNER_TYPE.

Which value should you use for businessPartner.type property?

You should use the name property values: “LEAD”, “CUSTOMER” or “SUPPLIER”.

As you can see, an enumeration contains translations (nameTranslations property). We use those translations in our iOS clients.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.