Appendix
Object fields
The following tables list only most important fields of most often used objects. For a full list please refer to the Vine Developer's Guide .
Company vy_company
Field Name |
Description |
NAME |
Object's name used internally |
Realname |
Official name of the company |
Location |
Extension to the name. |
Phone |
Telephone number |
Fax |
Fax number |
|
Email address |
WWWpage |
Company's Web site |
Address |
Mailing address |
Zip |
Postal code |
City |
City name |
State |
State |
StreetAddress |
Street address if the mailing address is a P.O. box |
Country |
Country name. parameter field: values in VP_COUNTRY |
Description |
Description of the object. |
Streetcity |
|
StreetZIP |
|
BUSINESSID |
|
CUSTOMERID |
|
DATASERVICEID |
stores key to external system maintaining the object. Currently used to store the Address Service Ids. For objects loaded or mapped to address service, it's always the key of object in the Address Service system |
COMPANYTYPE |
parameter field with values stored in the VP_COMPANYTYPE parameter table. |
OFFICETYPE |
VY_OFFICETYPE |
EDI |
|
LEADSCORE |
|
TURNOVER |
|
PROFIT |
|
PERSONNEL |
|
SALESTHISYEAR |
|
SALESLASTYEAR |
|
INDUSTRYGROUP |
|
INDUSTRYCODE |
VP_INDUSTRYGROUP |
COMPANYFORM |
VP_COMPANYFORM |
Person vy_person
Field Name |
Description |
LastName |
Last name |
FirstName |
First name |
Title |
Title, e.g. job description |
Department |
Department, unit in the company/location |
Phone |
Telephone number of the person |
Phone2 |
Additional phone, e.g. mobile |
Fax |
Fax number |
|
E-mail address |
HomePHONE |
Home phone |
HomeAddress |
Home address |
HomeZip |
Postal code |
HomeCity |
City name |
HomeState |
State |
HomeCountry |
Country name |
Description |
Description of the object. |
SKYPE |
|
ISUSER |
|
DECISIONMAKER |
VS_PERSONTYPE |
COUNTRYNAME |
VP_COUNTRY |
LEADSCORE |
|
LASTMARKETINGOPERATIONTYPE |
VP_MARKETINGOP_TYPE |
LASTMARKETINGOPERATIONDATE |
|
WEBPAGE |
|
DATASERVICEID |
stores key to external system maintaining the object. Currently used to store the Address Service Ids. For objects loaded or mapped to address service, it's always the key of object in the Address Service system |
MAINREPOSPONSIBLITY |
VP_MAIN_RESP_TYPE |
Event vy_event
Field Name |
Description |
NAME |
Name of the event |
StartDate |
Event start date or date with time |
StartDateGMT |
GMT time |
EndDate |
Event end date or date with time |
EndDateGMT |
GMT time |
EventPhase |
Phase of the event: 1 = 'not done', 2 = 'done' |
EventType |
ID of the event's type: see VY_EVENTTYPE |
RemindTime |
How many seconds before the event the reminder message is given (0 if no reminder) |
RemindType |
Remind type popup (0= dialog, 1=gsm) |
Description |
Description of the object. |
Location |
To store information about where the event happens |
Reported | VY_EVENT_REPORTED |
Project vy_project
Field Name |
Description |
NAME |
Name of the project |
ProjectPhase |
ID of the project's phase: see VY_PROJECTPHASE |
ProjectType |
ID of the project's type: see VY_PROJECTTYPE |
StartDate |
Project start date (or date with time) |
EndDate |
Project end date (or date with time) |
ProjectSum |
Project total (currency and actual meaning are up to customers) |
Budget |
Budget of the project (currency and actual meaning are up to customers) |
Amount |
Currency and actual meaning are up to customers |
ProjectLength |
Duration of the project (units and actual meaning are up to customer) |
Description |
Description of the object. |
Folder vy_collection
Field Name |
Description |
NAME |
Name of the folder |
ContentsType |
ID of the type of a connection which sets the type of folder members, see VY_CONNECTIONTYPE.ID |
Description |
Description of the object |
Resource vy_resource
Field Name |
Description |
NAME |
Name of the resource |
ResourceType |
ID of the resource's type, see VY_RESOURCETYPE.ID |
Description |
Description of the object. |
Document vy_document
Field Name |
Description |
NAME |
Name of the document |
DOCUMENTTYPE |
Type parameter field. VY_DOCUMENTTYPE |
DOCUMENTPHASE |
Phase parameter field. VY_DOCUMENTPHASE |
Description |
Description of the object. |
DOCUMENTDATE |
Sales Case vy_salescase
Field Name |
Description |
NAME |
Object Name |
salesunit |
VY_SALESUNIT |
salesphase |
VY_SALESPHASE |
startdate |
|
enddate |
|
offerdate |
|
salestype |
VY_SALESTYPE |
sales |
|
Sales2 |
|
Sales3 |
|
salesarea |
VY_SALES_AREA |
subject |
|
decisionphase |
VY_SALES_DECIS_PHASE |
Financestatus |
VY_SALES_FINA_STATUS |
Internalcompetition |
VY_SALESINTERNCOMPET |
Totalprobability |
|
salesprobability |
VY_SALESPROBABILITY |
Description |
Description of the object. |
Account vs_salesaccount
Field Name |
Description |
NAME |
Object Name |
salesarea |
VY_SALES_AREA |
Businessunit |
VY_SALESUNIT |
Wellbeing |
VS_SALESACC_BEING |
accountphase |
|
Details |
|
Comments |
|
Target |
|
Challenges |
|
Plan |
|
Description |
Description of the object. |
Service Request vs_servicerequest
Field Name |
Description |
NAME |
Object Name |
Caseid |
|
component |
|
startdate |
|
enddate |
|
note |
|
OtherInfo |
|
ServReqPhase |
VS_SERVREQ_PHASE |
PlatformType |
VS_PLATFORMTYPE |
PlatFormVersion |
|
PriorityType |
VS_PRIORITYTYPE |
ProductType |
VS_HDPRODUCTTYPE |
ProductVersion |
|
Published |
VS_SERVREQ_PUBLISHED |
Repeating |
VS_SERVREQ_REPEATING |
ResponsibleType |
VS_RESPONSIBLETYPE |
Severity |
VS_SERVREQ_SEVERITY |
Solution |
|
SolutionType |
VS_SOLUTIONTYPE |
ServReqType |
VS_SERVREQ_TYPE |
Version |
|
Description |
Description of the object. |
Questionnaire vs_questionnaire
Field Name |
Description |
NAME | |
ENDDATE | |
PHASE | VS_QUESTION_PHASE |
DESCRIPTION | |
STARTDATE | |
COMMON | |
DEFAULTQUESTIONNAIRE | VS_QUESTIONN_DEFAULT |
EVENTTYPE | VY_EVENTTYPE |
Web Link
Field Name |
Description |
NAME |
URL, e.g. https://vine.eu |
Description |
Description of the object. |
Object Parameters
Vine objects can have parameter fields, i.e. fields whose values can be chosen only from a fixed set of choices. This set of choices is stored in a separate parameter table whose name is given in the Description column for parameter object fields.
For example, this means that the EVENTTYPE field of Events references the VY_EVENTTYPE parameter table.
EVENTTYPE | VY_EVENTTYPE |
You will most likely only use the NAME field which stores the parameter value.
For example, to refer to event's type you can use the following substitution: [[EVENTNAME.EVENTTYPE]]